-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fail with copyfiles #6066
Comments
I am running into this today too. |
@sctgraham @aaronmarkle Are these brand new projects created from the interface or pre-existing projects just now seeing issues on recent deployments? |
@denolfe the latter : It was a local install that was configured and then pushed to the payload cloud. However, I was happily pushing changes without issue until today. |
Looks like there may have been some behavior changes in DO's platform: https://docs.digitalocean.com/products/app-platform/reference/buildpacks/nodejs/#specifying-devdependencies You might need to follow these steps and change your build command in your Payload Cloud Dashboard to be the one defined. This is just a workaround, we are actively working with them on a long-term solution. |
I swapped out 'copyfiles' with 'rsync' temporarily and named the npm command 'syncfiles'. Rsync comes pre-installed on most Linux distributions, simplifying the process.
The build script needs to be updated:
|
@denolfe yup that's it ! Thanks for that.
|
Link to reproduction
No response
Describe the Bug
My build on payload cloud is failing due to the
copyfiles
command. However, the dependency is installed and the yarn command is running fine locally.Thanks for any help on this ...
To Reproduce
This happened after upgrading my package dependencies.
This is the payload cloud log output :
Here are my package dependencies and scripts :
Payload Version
2.14.1
Adapters and Plugins
bundler-webpack, db-mongodb, plugin-cloud, plugin-redirects, plugin-seo, richtext-lexical
The text was updated successfully, but these errors were encountered: