22 days ago
Hello fellow entrepreneurs I’m 90% of the way this app I have no coding skills whatsoever but I managed to make it this far anyone who can please help thx All I can say is it goes back and forth between two errors
0 Replies
22 days ago
Have you tried removing that RUN command entirely? Railway will cache layers on it's own.
22 days ago
* Removing just the cache part, let me rewrite it for you
22 days ago
RUN npm ci --omit=dev --no-audit --no-fund
22 days ago
Change it to
RUN npm i --omit=dev --no-audit --no-fund
22 days ago
@Eric2Legit247 Better solution:
Delete package-lock.json on your local machine. Run npm i there. Then push the new file. Change the command back to the ci one.
Yes I will I think the building the image gonna time out cause it 7 mins in
22 days ago
Plesae check to see if your agent re-added the cache mount RUN command in the Dockerfile.
22 days ago
Can you share the entirety of the Dockerfile now?
22 days ago
It very much did add it back.

22 days ago
Delete that line yourself. Without the AI. Replace it with RUN прi ci --omit-dev --no-audit --no-fund
22 days ago
Perfect
22 days ago
Commit and it should automatically redeploy, yes
22 days ago
Did you yourself do the action of deleting package lock and reinstalling or did your agent?
22 days ago
Yes. Please. Open your terminal and run the following.
rm package-lock.jsonnpm i
22 days ago
You're in the wrong directory, run cd .. first.
22 days ago
Then run those two commands again.
22 days ago
Yellowbook

22 days ago
Awesomesauce
22 days ago
git commit -m "fix: update package-lock.json"
22 days ago
git push
22 days ago
Okay. Is this repository public?
22 days ago
Found it myself. Going to take a crack at it.
https://github.com/DrippyEric247/final10-backend
22 days ago
@Eric2Legit247 I notice you have two branches. Is Railway set to be using master rather than main?
22 days ago
@Eric2Legit247 I can build the image just fine. Can you delete the service, recreate it, and set the branch to master again?
22 days ago
I apologize, I missed the double directory. You do not need to delete the service.
Run these commands. By hand. Without AI.
cd serverrm package-lock.jsonnpm i
22 days ago
Yes. Not to be rude, but you need to stop using your agent for this. It has clearly proven to not understand the issue, and might go out and change other things.

22 days ago
All you need to do is open a terminal and copy paste the command I'm sending in. You do not need an AI for that.
22 days ago
Oh my. Somehow I missed that rm didn't work above.
It's del package-lock.json instead of the rm command
22 days ago
Can't believe I missed that even with Brody reacting…
22 days ago
del package-lock.jsonnpm i
22 days ago
<:frogsigh:1424892413314469988> Yeah try it.
22 days ago
After this I'm going to sleep
22 days ago
@Eric2Legit247 Did that end up working?
13 days ago
Hey, can you click on the view logs button and sends us the full logs?
13 days ago
is this your repository? https://github.com/DrippyEric247/final10-backend
13 days ago
accept the following PR and wait for Railway to deploy your code
https://github.com/DrippyEric247/final10-backend/pull/1
13 days ago
if you run into any issues, let me know
13 days ago
Railway should already be deploying your code
13 days ago
They have a whole bunch of branches with multiple implying main, as well as a whole bunch of different package locks in different directories
13 days ago
I've done another PR
https://github.com/DrippyEric247/final10-backend/pull/2
There I remove any node_modules folder which shouldn't be pushed and also fix the package locks
If after merging this PR nothing happens on Railway, please confirm that your services are using the master branch as the default.
12 days ago
Go to your service settings and look for "watch patterns"
12 days ago
and then remove it
11 days ago
Are you sure you're using the master branch on your service? I had no problems installing dependencies the last time
11 days ago
I see that it's a problem with the Dockerfile, give me a minute to debug it further.
11 days ago
Now that should do the trick:
https://github.com/DrippyEric247/final10-backend/pull/3
11 days ago
explanation: you were using a .npmrc file which wasn't included in the Dockerfile, thus causing package-lock.json differences.






















