an hour ago
I have two problems:
- stale pre-deploy command persists even if I push substantial code changes -- config has new command, but logs show that old command failed.
- same for build command
finally I asked the agent to "please run a fresh deployment from scratch" but I believe it's much easier to add a "clear cache" button to deployments.
your call, of course -- but this has caused me significant headaches on multiple projects already.
thanks for listening!
1 Replies
an hour ago
Your service config is currently correct with no pending uncommitted changes, so the pre-deploy and build commands are being picked up fresh on each deployment. What persists between deploys is the build layer cache (cached dependencies and build artifacts), not the config values themselves. To force a fully clean build, add a service environment variable named NO_CACHE with a value of 1, which disables all build layer caching. For more granular control, the RAILPACK_DISABLE_CACHE variable lets you target specific caches or disable all of them by setting its value to a single asterisk.
Status changed to Awaiting User Response Railway • about 1 hour ago
Status changed to Solved lukaramishvili • 8 minutes ago