The Start command is the command MyKinsta needs to start your application. It’s a must for any application, whether it’s created with a buildpack or Dockerfile. The Start command may differ depending on the application’s language. We’ve provided examples from some common languages below.

When an application is created with a buildpack, we attempt to infer the Start command based on the contents of your application’s repository, or you can specify the Start command in the Resources step when you add the application. To add multiple Start commands, use && to chain the commands together like: command one && command two.

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.

Kinsta shows the Start command used for the rollout of the deployment in Deployment details. In Deployments > History, select a deployment to view the details and Rollout process in the details.

Successful rollout process in Deployment details.
Successful rollout process in Deployment details.
Failed rollout process in Deployment details.
Failed rollout process in Deployment details.

Python

  • Python: python3 main.py
  • Django: gunicorn .wsgi

Go

Go: bin/<repo name>

PHP

  • PHP: heroku-php-apache2
  • Laravel:
    • heroku-php-apache2 /public
    • php artisan serve --host 0.0.0.0 --port 8080
  • Statamic: heroku-php-apache2 public/

Node.js

Node.js

npm start

If you would like to use another command, you need to modify the web process in MyKinsta.

"scripts": {
"start": "node server.js"
},

Node.js with a Dockerfile

When you create the app Kinsta creates a process from the CMD instruction.

CMD ["npm", "run", "start"]

If you change this command in the repository, the process is not changed by default, so you must edit the process in your application’s Processes in MyKinsta.

Ruby

Ruby on Rails: When you first create the application, Kinsta creates a process from the ENTRYPOINT instruction.

ENTRYPOINT ["entrypoint.sh"]

If you change this command in the repository, the process is not changed by default, so you must edit the process in your application’s Processes in MyKinsta.

Java

Java: When you deploy an application, Kinsta automatically creates processes based on the Procfile in the root of the repository.

Scala

Scala: target/universal/stage/bin/ -Dhttp.port=$PORT