a year ago
this is the logs:
[Region: us-west1]
==============
Using Nixpacks
==============
context: bcb5c8d7bc44c3c408474145fbd6e787
╔════════ Nixpacks v1.29.1 ═══════╗
║ setup │ nodejs_18, npm-9_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ start │ npm run devStart ║
╚═════════════════════════════════╝
[Region: us-west1]
==============
Using Nixpacks
==============
context: b2879eafd5ad9a48eda9fc518133fca0
╔════════ Nixpacks v1.29.1 ═══════╗
║ setup │ nodejs_18, npm-9_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ start │ npm run devStart ║
╚═════════════════════════════════╝
#0 building with "builder-bi9o" instance using docker-container driver
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 2.35kB done
#1 DONE 0.0s
#2 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1731369831
#2 DONE 0.1s
#3 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1731369831@sha256:248c718af9f76e602170a3cdbf69658edf55c910023104e1f277e517b77977a0
#3 resolve ghcr.io/railwayapp/nixpacks:ubuntu-1731369831@sha256:248c718af9f76e602170a3cdbf69658edf55c910023104e1f277e517b77977a0 done
#3 DONE 0.0s
#4 [stage-0 4/10] RUN nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d
#4 CACHED
#5 [internal] load .dockerignore
#5 transferring context: 2B done
#5 DONE 0.0s
#6 [internal] load build context
#6 transferring context: 2.20MB 0.0s done
#6 DONE 0.0s
ⓘ Deployment information is only viewable by project members and Railway employees.
1 Replies
a year ago
Hey, looks like your latest deployment is up and running!
But I see that you are using nodemon in a production environment.
This can be solved by changing the start command in the service settings to node server.js
Status changed to Solved brody • over 1 year ago