Hey, thanks for this Paperclip template on Railway — it's a great starting point.

I have a practical question: Railway templates seem to be pinned to a specific version of Paperclip at the time they were created. Since Paperclip development is very active (near-weekly releases), how do you handle updates on the template side?

Concretely, if I deploy today using your template, is there a straightforward way to stay on the latest version of Paperclip without having to reconfigure everything from scratch each time? Are you pulling from the official latest Docker image, or pinning to a specific version?

Thanks!

Hey, you can refer the git repo which is powering this template, but in short, I am using the latest version of Paperclip, as mentioned in package.json.

So if you have already deployed Paperclip, and a new version is out there, you just need to go to Paperclip service in railway > Redeploy it. It will fetch the latest version and install it while keeping your existing data intact. Nothing extra to configure.

-------

For maintenance, I generally deploy this template myself and keep checking if newer versions are properly compatible with the existing repo or needs update.

If there are any updates required in the code, I update and push to git.

And you can download that update to your existing configured Paperclip by going to Paperclip service > Network tab > 'check for updates' (below the branch name of git repo) > and if there is any update you can just click update and it will be redeployed.

Hi - also, thanks for this Paperclip template. I am following the redeploy process and my company icons keep getting wiped out and I need to reset them after redeploying Paperclip on Railway. Any thoughts on why this might be happening and what I can do to prevent in the future?

hey thanks for highlighting this. turns out that there was change in directory layout in one of the latest releases, so file uploads were not being persisted since they were not saved in the volume. Just pushed a fix - added a PAPERCLIP_STORAGE_LOCAL_DIR env var that points to the volume, so it'll persist across redeploys now. Pull the latest and redeploy and you should be good, let me know if you face any issues!