learning-path.md

copyright	lastupdated	keywords	subcollection
years 2024	2024-10-17	learning paths, code engine, deployments, tools, applications, jobs, project, log, monitor	codeengine

{{site.data.keyword.attribute-definition-list}}

Learning paths for {{site.data.keyword.codeengineshort}}

{: #learning-paths}

Find your path to accomplish what you want with {{site.data.keyword.codeenginefull}}. {: shortdesc}

Plan your deployments

{: #lp-plan-deployments}

Before you start, learn about {{site.data.keyword.codeengineshort}} and some common terms.

Then, decide whether you want to deploy an application, create a job, or run a function by reading planning for {{site.data.keyword.codeengineshort}}.

You can even try out our application tutorial, our job tutorial, or our function tutorial.

Install the tools

{: #lp-install-tools}

If you plan to use the CLI, you must install it. As you work with your {{site.data.keyword.codeengineshort}} workloads, refer to the CLI command reference and track CLI version updates with the CLI change log. You can also access the {{site.data.keyword.cloud-shell_notm}} in your web browser.

If you do not want to use the CLI, you can work from the console{: external}.

Create your first project

{: #lp-set-environment}

To get started with {{site.data.keyword.codeengineshort}}, create a project to contain your entities. You can also set access policies for your project.

Need help? Check out troubleshooting tips for projects. If you need more help, try getting support.

Develop your application, job, or function

{: #lp-develop-app-job}

{{site.data.keyword.codeengineshort}} deploys applications and runs jobs that are bundled into container images. If you do not have a container image, you can build and deploy your code from within {{site.data.keyword.codeengineshort}}.

{{site.data.keyword.codeengineshort}} runs functions as code bundles. If you do not have a code bundle, you can build and run your function from within {{site.data.keyword.codeengineshort}}.

Do you have source code or a container image for your application or job?

{: #lp-develop-app-job-source-code-image}

I have a container image.

• If your image is stored in a container registry that you have access to, then you are ready to deploy.
• If your image is in a private registry, either in a different {{site.data.keyword.registryshort}} account or in private registry such as Docker Hub, you must set up access.

Then, you are ready to deploy your application, run your job, or run your function.

I have source code.

• Find out what advantages are available when you build your image with {{site.data.keyword.codeengineshort}}.

• Plan for your build.

• You can also find tips for creating a Dockerfile.

• If your source code is in a private repository, set up access.

• Optionally, set up an {{site.data.keyword.registrylong_notm}} namespace to hold your built image. If the {{site.data.keyword.registryshort}} namespace is in a different account, set up access. If you do not set up access to your {{site.data.keyword.registrylong_notm}} namespace, access is created automatically for you.

• Build your source code.

Need help? Check out troubleshooting tips for builds. If you need more help, try getting support.

Deploy your application

{: #lp-deploy-app}

To get started, read plan a container image for {{site.data.keyword.codeengineshort}} applications and Application workloads.

How does your application scale?

{: #lp-deploy-app-how-app-scale}

See Configuring application scaling.

Do yo want to customize your application?

{: #lp-deploy-app-customize-app}

• Does your application require a project endpoint? See Deploying your app with a project endpoint.
• Does your application require a private endpoint? See Deploying your app with a private endpoint.
• How much CPU and memory does your application need? See Supported memory and CPU combinations.
• Do you have commands and arguments to add to your application? See Deploying your app with commands and arguments.
• Want to define environment variables for your application? Find out how with Working with environment variables.
• Does your application take advantage of configmaps or secrets? Take a look at Working with secrets or Working with configmaps.
• Do you want to deploy your app in a toolchain? See Integrating Code Engine workloads with Continuous Delivery.
• Do you want to use Terraform to deploy your app? Find out more with Setting up Terraform for Code Engine.

Are you ready to deploy?

{: #lp-deploy-app-ready-to-deploy}

• Deploy application workloads from a public repository.
• Deploy application workloads from images in {{site.data.keyword.registryshort}}.
• Deploy application workloads from images in a private repository.

Make your app highly available by deploying it in multiple regions.

Do you want to add more customizations?

{: #lp-deploy-app-add-customizations}

• Want to integrate with other {{site.data.keyword.cloud_notm}} services? See Integrating {{site.data.keyword.cloud_notm}} services with service binding.
• Want to connect an event producer to your application? See Subscribing to event producers.

Are you ready to access your application?

{: #lp-deploy-app-ready-to-access-app}

• Access the application.
• You can also create a custom domain mapping for your app.

Each update of an application configuration property creates a new revision of the application.

• Find information to update your app.

You can use Iter8 to validate your application code and latency and then determine if your revision is ready to use or if you must roll back to a more stable version.

Need help? Check out troubleshooting tips for applications. If you need more help, try getting support.

Run your job

{: #lp-run-job}

To get started, read plan a container image for {{site.data.keyword.codeengineshort}} jobs and Batch job workloads.

Do you want to create a job definition?

{: #lp-run-job-create-job-definition}

By creating a job definition, you can more easily run your job multiple times based on your configuration.

• Create a job from a public repository.
• Create a job from images in {{site.data.keyword.registryshort}}.
• Create a job from images in a private repository.

Do you want to run a job without first creating a definition?

{: #lp-run-job_run-job-without-definition}

With the CLI, you can submit a job run without first creating a job configuration. You can specify the same configuration options on the jobrun submit and jobrun resubmit commands that are available with the job create command.

• Run a job with the CLI without first creating a job configuration.

Do you want to customize your job?

{: #lp-run-job-customize-job}

• How much CPU and memory does your job need? See Supported memory and CPU combinations.
• Do you have commands and arguments to add to your job? See Deploying your application with commands and arguments.
• Want to define environment variables for your job? Find out how with Working with environment variables.
• Does your job take advantage of configmaps or secrets? Take a look at Working with secrets or Working with configmaps.
• Do you want to deploy your app in a toolchain? See Integrating Code Engine workloads with Continuous Delivery.
• Do you want to use Terraform to deploy your app? Find out more with Setting up Terraform for Code Engine.

{{site.data.keyword.codeengineshort}} supports Lithops for running jobs. See running jobs with Lithops framework.

Are you ready to create and run your job?

{: #lp-run-job_ready-to-create-run-job}

You can run your job directly or create a job definition and run your job based on that configuration.

• To run a job directly, see Run a job with the CLI without first creating a job configuration.
• To run a job from a job definition, see run a job.

Do you want to add more customizations?

{: #lp-run-job-add-customizations}

• Want to integrate with other {{site.data.keyword.cloud_notm}} services? See Integrating {{site.data.keyword.cloud_notm}} services with service binding.
• Want to connect an event producer to your job? See Subscribing to event producers.

Need help? Check out troubleshooting tips for jobs. If you need more help, try getting support.

Run your Function

{: #lp-run-fun}

To get started, read Working with Functions and Function workloads.

Functions use a managed runtime. Find out more at Runtimes.

Do you want to customize your function?

{: #lp-run-fun-customize}

• How much CPU and memory does your function need? See Supported memory and CPU combinations.
• Want to define environment variables for your function? Find out how with Working with environment variables.
• Does your function take advantage of configmaps or secrets? Take a look at Working with secrets or Working with configmaps.

Areyou ready to deploy?

{: #lp-run-fun-ready-to-deploy}

• Creating Function workloads with inline code.
• Creating Function workloads with repository source code.
• Creating Function workloads from local source code.

Do you want to add more customizations?

{: #lp-run-fun-add-customizations}

• Want to integrate with other {{site.data.keyword.cloud_notm}} services? See Integrating {{site.data.keyword.cloud_notm}} services with service binding.

Log and monitor your workloads

{: #lp-log-mon}

Logging can help you troubleshoot your applications, jobs and functions. See Viewing logs.

You can also view, manage, and audit user-initiated activities that occur in your {{site.data.keyword.codeengineshort}} project.

Finally, analyze performance metrics by collecting information with {{site.data.keyword.mon_full_notm}}. You can create custom dashboards to monitor {{site.data.keyword.codeengineshort}} workloads.

Migrate your workloads

{: #lp-migrate}

If you are moving from a different service to Code Engine, there are several topics that can help you.

• Migrating IBM Cloud Functions to Code Engine.
• Getting started with your migration from Heroku to Code Engine.
• Getting started with your migration from Cloud Foundry to Code Engine.