#Problems deploying

30 messages · Page 1 of 1 (latest)

silver dawn
#

Quick question is it possible to deploy a payload app on simple webhosting providers? Meaning uploading "build" & "dist" via ftp to webhosting and starting from there?

tawdry ridgeBOT
nova thunder
silver dawn
#

which node process do you mean exactly? i built it locally, can i move it to hosting with ftp ?

nova thunder
#

Yes, you'll need to move the build and dist directories

#

Along with an .env file if you use one.

#

Then you'd do node dist/server.js assuming you're using one of our templates

tawdry ridgeBOT
coral osprey
#

I am having issue while deploying

#

I am using ecommerce template

#

I built it locally and moved build and dist folders

#

mapped them docker compose file

#

please find docker-compose file above

#

any help

# 
volumes:
      - ./payload:/home/node/app
      - ./node-modules:/home/node/app/node_modules
#

i uploaded locally built folders (build and dist) to payload and mapped that in docker-compose file

# 
$ cross-env PAYLOAD_CONFIG_PATH=dist/payload/payload.config.js NODE_ENV=production node dist/server.js
unhandledRejection [Error: ENOENT: no such file or directory, open '/home/node/app/.next/BUILD_ID'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/node/app/.next/BUILD_ID'
}
#

getting above error

# 
yarn install v1.22.19
[1/4] Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "jackspeak@^2.3.5"
success Already up-to-date.
Done in 3.87s.
yarn run v1.22.19
$ cross-env PAYLOAD_CONFIG_PATH=dist/payload/payload.config.js NODE_ENV=production node dist/server.js
unhandledRejection [Error: ENOENT: no such file or directory, open '/home/node/app/.next/BUILD_ID'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/node/app/.next/BUILD_ID'
}
[13:53:39] INFO (payload): Connected to MongoDB server successfully!
[13:53:39] INFO (payload): Starting Payload...
[13:53:39] INFO (payload): Payload Admin URL: https://payload.example.com/admin
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1
#

any help

coral osprey
#

i was able to resolve the /home/node/app/.next/BUILD_ID error

#

but after that getting above error

leaden grove
#

Any updates on that one @coral osprey ? I’m having the same issue

worn owl
#

@coral osprey how did you fix this issue?

gentle cove
#

@coral osprey I have the same issue with [Error: ENOENT: no such file or directory, open '/home/node/app/.next/BUILD_ID'].
It would be really nice if you share how you fixed it. Thanks

royal wraith
royal wraith
#

So, this worked for me.
Posting here for anyone struggling with the same error.
Issue : https://github.com/payloadcms/payload/issues/3992#issuecomment-1792742215
Basically Update the Dockerfile with this
https://github.com/payloadcms/payload/pull/4029/commits/e61d1761da9c668cdfe2373c0610bd28af9babe9#diff-e1c681d2ddfe02367a933715fd0d31f9bf27fbe3104efb30ae67c5da9a992e1e

GitHub
fix: add missing `.next` directory to docker builds where required ...

Description
Fixes #3992 - missing .next directory from build container.
Additionally, add .dockerignore entries to avoid package version conflicts.

I have read and understand the CONTRIBUTING.md ...

GitHub
Provided Dockerfile - Build missing `.next/BUILD_ID` · Issue #3992 ...

Link to reproduction No response Describe the Bug I've built the provided Dockerfile from npx create-payload-app my-project -t website pushed my image to dockerhub and I'm currently trying ...

maiden dust