this is strange. Did you click on 'Update' on the deployed project page? It should fetch the latest changes from the template -

In case you still dont see it, just add PAPERCLIP_STORAGE_LOCAL_DIR a new var with value - `${{RAILWAY_VOLUME_MOUNT_PATH}}/storage` & you should be good to go.

Let me know if you still face any issues.

Hi - thanks for this info. I will add manually. But can you give me some additional info on where the 'update' option is located in Railway? I am using the 'Redeploy' from the project. I must be doing something wrong and want to be sure I get it right for any future updates. Screenshot attached of what I am doing to Redeploy.

So generally, I have seen when there's an underlying change in template repo, there's an 'Update' button available somewhere on top left.

Although I just tried deploying one of the templates and then updating the underlying template to test it, but I also dont see the 'Update' button here. Not entirely sure why Railway is not capturing the update

so i think based on Railway's docs, the changes are captured only when there is any change in the 'repo' powering the template, and not the changes otherwise like env variable changes -

Will clarify with the railway team. But thanks for pointing this out!

Ahhh - okay - very interesting. I do not see that update option either. For now I am assuming that adding the variable manually will take care of the persistence issue and we can sort out the Railway update process? Or, is that storage persistence still an issue even if I add the variable manually?

yes, you can sort out the persistence issue by only adding the additional env variable mentioned above.

Let me know if you face any issues!

Roger that - will do. I am so appreciative of your creating this project. Totally awesome!