2 years ago
A deployment build error from Nixpacks says there is no 'start' command. This is as far as I get:
Nixpacks build failed
╔══════════════════════════════ Nixpacks v1.21.2 ══════════════════════════════╗
║ setup │ python38, gcc ║
║──────────────────────────────────────────────────────────────────────────────║
║ install │ python -m venv --copies /opt/venv && . /opt/venv/bin/activate ║
║ │ && pip install -r requirements.txt ║
║──────────────────────────────────────────────────────────────────────────────║
║ start │ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Where do I specify the start command?
ⓘ Deployment information is only viewable by Project members and Railway admins.
1 Replies
2 years ago
Where do I specify the start command?
In a railway.json file, you would need to use gunicorn, here an example -
https://github.com/railwayapp-templates/flask/blob/main/railway.json#L7C26-L7C43