When not working with Dockerfiles, we use buildpacks to deploy applications. Buildpacks are scripts that are run when your application is deployed to install dependencies for your application and configure your environment.

Some applications will require no configuration, but some will require specialized commands and options to run.

Environment Variables

If your application requires environment variables to be set, you can do so in MyKinsta. Head over to Environment Variables for more information.

Defining Processes on MyKinsta

When deploying an application, Kinsta will set a default command for some processes like the web process. For a Node.js application, this would be npm start. You can define your own commands on MyKinsta in the Processes section of your application. You can see an example of this in our Example Deployment.

Defining Processes in a Procfile

Procfiles define processes from your application’s code and should be committed to your repository. A Procfile contains one process per line in the following format:

process_name: command

For example, to run a Laravel application, you might want to use the following:

web: php artisan serve --host --port 8080

If you are using a Procfile, you will need to define a process named web to ensure the container will fulfill web requests.

Adding and Editing Buildpacks

You can manage buildpacks on your application’s Settings page. To add additional build packs, click the Add buildpack button. To remove or change the order of your application’s buildpacks, click the Edit buildpacks button.

When you add a buildpack, it’s automatically added to the end of the buildpacks list, so you may need to edit the order of your buildpacks. You can drag and drop the buildpacks to change their order in the Edit buildpacks modal/pop-up.