Here are just a few of the languages we support and have tested:
Adding an Application
To add an application, click Add service on the Applications page and select Application from the dropdown menu.
The first time you add an application, you’ll need to select a Git service provider and repository from your account. You can choose from any (or all) of the following:
Once you’ve connected your Git provider account, you’ll be returned to MyKinsta to continue with the rest of the Add application steps.
The following fields are available in the multipart form with the described effects.
You have the option here to select from any of the supported Git service providers.
- Repository: Select the Git Repository to use.
- Default branch: Set the branch that will be deployed on changes and manually.
- Automatic deployment on commit: Check this box to automatically deploy your application each time a commit is made to the branch selected above.
- Application name: This name will be displayed in MyKinsta for easy reference.
- Data center location: Choose the data center you want to use for this application.
Environment variables feed your application information from outside of the running of the application. They typically set things like database connection details and API keys. Expand this section to enter any environment variables for your application and select if the variables are to be available during runtime and/or the build process.
The build environment dictates how we build your application.
Choose the build machine needed to build your application. The more resources the build machine has, the faster the build process will run.
- Set up container image automatically: Choose this option to have Kinsta use a buildpack to create a container for your application based on your repository. We’ll try to automatically determine the best environment for your project and create a container for it. If no version is specified, we’ll use the latest available version for the language your application is written in. If you want to use a different language version for your application, set the version in your application’s files.
- Build path: The path in the repository to the files required to build the application. Most applications are built from the repository root, and the Build path defaults to this (.). If you have a different build path, specify it here. For example, if your application needs to be built from a subdirectory (e.g. app), enter that subdirectory path in the Build path field: app.
- Use Dockerfile to set up container image: If you want more control; or already have things set up in a Dockerfile in your repository, select this option and set the Dockerfile path and Context. With a Dockerfile, you can use almost any language.
- Dockerfile path: The path to your Dockerfile relative to the repository root. For example, if your Dockerfile is in the repository root, enter Dockerfile in that field. If your Dockerfile is in a subdirectory named app, enter the path to the Dockerfile: app/Dockerfile.
- Context: The path in the repository we need access to so we can build your application. Most applications are built from the repository root, and you can enter the repository root (.) in the Context field. If your application needs to be built from a subdirectory (e.g. app), enter that subdirectory path in the Context field: app.
This allows you to set the resources and start command for your processes. You also have the option to add persistent storage to the web process or background processes. You cannot add persistent storage to a cron job.
Set up your processes
- Process name: This name will be displayed in the list of the application’s processes for easy reference. The web process is added automatically. If you want to rename it, you can.
- Process type: For the automatically added web service, this cannot be changed. If you need to add additional processes like a background worker or cron job, you can add them here or on your application’s Processes page after deployment.
- Start command: Enter the start command for your web process. If you leave this blank, we’ll try to detect it during deployment. The start command for a process can also be edited on your application’s Processes page after deployment. The start command is required for any additional processes you add.
- Pod size: Choose the pod size for your process. This determines the CPU and RAM dedicated to the process.
- Note: If you choose a Hobby pod size for your web process, you will not be able to add a custom domain to your application. If you need a custom domain for your application, you can upgrade this anytime.
- Instance count: The number of instances for the process, up to a maximum of 50. Each instance represents one pod, and the instances all use the same pod size; you cannot define a different pod size for each instance. Note: If you add persistent storage to a web or background process, those processes are limited to one instance each.
- Disk: To add persistent storage to a web or background process, click Disk to expand this section and complete the following:
- Mount path: Specify the location of the files to be added to persistent storage (e.g. /var/lib/data). This cannot be the root directory or the directory of any configuration files. See the Persistent Storage doc for the full list of invalid mount paths.
- Size: Choose the disk size for your persistent storage volume. You can increase the disk size at any time (on the application’s Disks page), but you cannot downgrade the disk size once it has been created.
Confirm your billing details, adding a new payment method if needed.
Review your application’s monthly usage costs and confirm your payment method.
Click Confirm payment method.