Hey there! We've found the following might help you get unblocked faster:

• 📚 No Start Command Could be Found

• 🧵 Failed to start application: PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.

• 🧵 Error: No start command could be found

If you find the answer from one of these, please let us know by solving the thread!

I solved no start command issue by changing my .gitlab-ci.yml from

railway up --service api

to

cd apps/api && railway up --service api && cd ../..

But after that it's failing for docker issues. I haven't found a full solution yet. Any recommendations would be appreciated.

Looking at https://docs.railway.com/guides/monorepo#deploying-a-shared-monorepo, which reflects how my project is configured, I have the following questions

1. Is there railway up involved? Which service would it specify?

2. How do I exactly upload the code from .gitlab-ci.yml into railway?

3. Do I have separate build commands for each service?

4. Are the shared vars available during build?

Trying the approach in the document above.
.gitlab-ci.yml command

railway up --service api --detach

But back to no start command

↳ Detected Node
↳ Using npm package manager
↳ Installing npm@10.7.0 with Corepack
✖ 
No start command was found

.
 
To configure your start command, Railpack will check:
 
1. A "start" script in your package.json:
"scripts": {
"start": "node index.js"
}

Hello,

You change the build and start commands to cd into the directories for each app in the monorepo

I don't have package.json in each app. Do I need to create one for each?

Update:
1. I didn't create service specific package.json (more difficult to maintain).

2. I had changed build and start commands but did not realize that I had to apply those changes before they take effect.

3. Once I applied those changes, the no start command error went away.

So to clarify. This solved your issue?

Yes, it's solved. Thanks.