Go Live Checklist

Follow the go-live checklist to ensure you have everything ready to get your application up and running quickly on Kinsta’s Application Hosting. If you run into any problems or have questions, our Support team is available 24/7, and we’re happy to help.

To help you get started with Application Hosting, you can use one of our example templates on GitHub, or you can use a public Git repository or Docker image.

1. Git Repository or Docker Image

You must ensure the application you want to host exists within a Git repository or Docker image.

If you use a public Git repository, you need the URL and branch of the repository. If you want to use a private Git repository, you must select a Git service provider and repository from your account. You can choose from any (or all) of the following:

If you use a public Docker image you need the path to the Docker image. If you want to use a private Docker image, you must add your registry credentials within username > Company settings > Registry credentials. You can choose from any (or all) of the following registries:

  • GitHub (ghcr.io)
  • GitLab (registry.gitlab.com)
  • Docker Hub (docker.io)

2. Environment Variables

Ensure you have all of the required Environment variables for your 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.

3. Build Path

An incorrect build path can cause the application deployment to fail. This is 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, you must specify this when you add the application, or you can change it in Settings (SettingsBuild > in the Environment section, click Change environment). 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.

4. Start Command or ENTRYPOINT

The Start command for the web process starts your application. If this is incorrect, the application will not run. You can specify the Start command when you add an application or within Processes click edit on the Web process.

If your application uses a Dockerfile to set up your container image, you must specify the ENTRYPOINT in the Dockerfile to run a container. For more information about how to specify your application’s ENTRYPOINT, see the Dockerfile reference.

For more details about what command to use based on your application’s language, see the examples provided in Application Start Command.

5. Background Workers and Cron Jobs

Determine if your application requires additional processes like a background worker or cron job; you can add these on your application’s Processes page after deployment.

6. Disk or Persistent Storage

If your application requires persistent storage, you can add this to your web process when you add your application. After you’ve added your application you can add persistent storage to your web process and background workers within Disks.

If you require persistent storage, you need to know the location of the files within your application to be added to the persistent storage disk, so you can specify this in the Mount path.

7. Add Your Domain to Kinsta

After you’ve confirmed your site is all good, it’s time to go live with your custom domain. Check out our Application Hosting Domains guide.

Was this article helpful?