Introducing Livops 2.0! Promo codeCEOgives you 8,000 so‘m on your balance.What’s new
Errors / No start command

Errors

No start command

no_start — we did not find the command that starts the app or bot. What we look for and how to set the command.

no_start — the project built, but we did not find the command that starts it. Write it in Settings → Start, or add one of the following to the project.

Node

We look for the start script in package.json, then the main field, then the files index.js, server.js, app.js, main.js.

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

In a TypeScript project, build first and start the built file: "start": "node dist/main.js".

Python

We look for:

  • a web: line in a Procfile;
  • manage.py — Django;
  • app = FastAPI() or app = Flask(__name__) in main.py, app.py or server.py (also in a package one or two folders down);
  • a Streamlit app;
  • for a bot: bot.py, main.py, app.py, run.py, src/<package>/__main__.py, or a file with if __name__ == "__main__".

If none is there, write the command in Settings yourself:

.venv/bin/python main.py

For a package — .venv/bin/python -m mybot.

Procfile

In any language you can put a Procfile at the project root:

web: node server.js
worker: .venv/bin/python bot.py

worker: for a bot, web: for a site or an API.

Go, Rust, Java

Here the program is built during the build and starts by itself. If you see no_start, it is usually a library — see This is a library.

Got a question? — @livops_uz