We're in the process of migrating from Nixpack to Railpack and running into the issue where the `startCommand` in the `deploy` property is not being recognized by Railway. See the config and error below. Gotten from the docs here: ``` { "$schema": "https://schema.railpack.com", "steps": { "install": { "commands": [ "pnpm install" ] }, "build": { "inputs": [ { "step": "install" } ], "commands": [ "moon backoffice-api:build" ] } }, "deploy": { "startCommand": "moon backoffice-api:start" } } ``` ``` ✖ No start command detected. Specify a start command: https://railpack.com/config/file ```

railpack.json startCommand not recognized

uturntech

PROOP

15 days ago

We're in the process of migrating from Nixpack to Railpack and running into the issue where the startCommand in the deploy property is not being recognized by Railway. See the config and error below. Gotten from the docs here: https://railpack.com/config/file

{
    "$schema": "https://schema.railpack.com",
    "steps": {
        "install": {
            "commands": [
                "pnpm install"
            ]
        },
        "build": {
            "inputs": [
                {
                    "step": "install"
                }
            ],
            "commands": [
                "moon backoffice-api:build"
            ]
        }
    },
    "deploy": {
        "startCommand": "moon backoffice-api:start"
    }
}

 ✖ No start command detected. Specify a start command: https://railpack.com/config/file

Solved$20 Bounty

2 Replies

Status changed to Open Railway • 15 days ago

mightatnight

HOBBY

15 days ago

Try to force redeploy without cache, should help

savagejayog

HOBBYTop 10% Contributor

15 days ago

Ive ran into this same issue migrating from Nixpacks. Railway ignored my railpack.json because the project was still set to use Nixpacks, so deploy.startCommand never got picked up.

Do this:

Put railpack.json in the repo root.
Make sure the Railway builder is set to Railpack, not Nixpacks.
Check for overrides like a Procfile or the RAILPACK_START_CMD env var.
Validate your JSON and schema so the file doesn't get silently skipped.

Also, as a quick test, set RAILPACK_START_CMD="moon backoffice-api:start" in your env to confirm the command works. If that doesn't help, paste the build log lines around config detection and I can take a look.

Status changed to Awaiting User Response Railway • 15 days ago

Railway

BOT

8 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 8 days ago

Welcome!