Settings

On your application’s Settings page, you can find details about your application, manage settings like buildpacks, and suspend or delete it.

General

This section shows general information about your application. The information shown depends on whether you use a Git repository or a Docker image.

Git repository

• Application name: This is the name of your application in MyKinsta.
• Repository and branch: The Git repository and branch.
• Automatic deployment on commit: When this box is checked, your application will automatically deploy each time a commit is made to the branch selected above.

To change any of the details, click Edit details. If you change the Branch, you must manually deploy your application again, which you can do on the Deployments page.

Docker image

• Application name: This is the name of your application in MyKinsta.
• Docker image: This is the path to your Docker image.
• Registry provider: If you use a private Docker image, the registry provider is shown here. You can access private Docker images from GitHub (ghcr.io), GitLab (registry.gitlab.com), or Docker Hub (docker.io) registries.
• Registry credential: This shows the name of the registry credentials set up within Company settings > Registry credentials.

To change the application name or registry credentials, click Edit details. If you change the Registry credential, you must manually deploy your application again, which you can do on the Deployments page.

Build

Resource

This shows the build machine you are using to build your application. The more resources the build machine has, the faster the build process will run. To change your build machine, click Update resource. If you change your build resource, you must manually deploy your application again, which you can do on the Deployments page.

Environment

This shows which environment type is used to build your application and the build path.

To change the build environment, click Change environment, and select from one of the following:

• Nixpacks: Use Nixpacks to create a container for your application based on your repository.
  • Build path: 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, specify it here. For example, if your application needs to be built from a subdirectory named app, enter app in the Build path field. This is also useful if you have a monorepo.
• Buildpacks: Use Buildpacks to create a container for your application based on your repository.
  • Build path: 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, specify it here. For example, if your application needs to be built from a subdirectory named app, enter app in the Build path field. This is also useful if you have a monorepo.
• Dockerfile: Use a Dockerfile (stored in your repository) to create a container for your application.
  • Dockerfile path: This is 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: This is 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. For example, if your application needs to be built from a subdirectory named app, enter app in the Context field.

If you change the environment, you must manually deploy your application again, which you can do on the Deployments page.

Buildpack

This section is only visible if your application’s container image is created with a Buildpack. You can view and manage your application’s buildpacks here. If you add or edit buildpacks, you must manually deploy your application again, which you can do on the Deployments page.

Danger zone

Suspend or resume application

There may be times when you need to stop an application without deleting it. This can be useful if you need to troubleshoot issues or test parts of the application without it running.

Suspending the application doesn’t change or remove anything from it. Connections to the application remain in place but will not work while the application is suspended. You will not incur any costs for the application during the suspension.

Click Suspend application and confirm the suspension by clicking Suspend application again in the modal/pop-up.

When you’re ready to restart your application, click Resume application and confirm the restart by clicking Resume application again in the modal/pop-up.

Delete application

If you no longer need the application, click Delete application, enter your application name, and click Delete application again to remove it completely.

Deleting the application completely removes the following:

• All files
• Settings
• Persistent storage disks
• Connections to other applications or databases.