Envoyer, maintain user uploads between releases

Isn't it the storage folder? I can't remember exactly from Jeffrey's series. Have you watched it?

@mstnorris Yea I think I need to move the uploads folder to the storage directory. Not sure how to display an image that is not stored in the public folder though. Do you know how? I don't recall this being covered in the videos.

Laravel Helpers maybe? Not entirely sure ;)

@mstnorris storage_path() seems to returns the path from the root of the server. So when I add it to the html, the link it generates is my-site.com/[path to storage directory]

This might be handy for you:

https://laracasts.com/discuss/channels/general-discussion/handling-uploaded-local-files-with-envoy?page=1

I had the same problem on a project of mine.

I solved it by moving the uploads directory one level up (where the current, releases and storage directories are) and used a deployment hook to create a symbolic link in the public directory.

You can also move it in the storage directory if you prefer, should work the same.

@foxted could you share the deployment hook?

I'm trying to use OpenVBX (a Twilio powered phone system) that needs to be accessible from the public directory. I added it to my project under public/vbx but every time I deploy it's starting from scratch, so it wipes out whatever files it generates after installing (so basically an installation loop, having to re-install after every deployment).

This is a hugely annoying issue at the moment. I thought that the public directory wasn't messed with by Envoyer, must have misunderstood that.

@opheliadesign

1. Create your VBX folder in /home/forge/{domain_name} or /home/forge/{domain_name}/storage
2. Create the deployment hook:

cd {{release}}/public
ln -s /home/forge/{domain_name}/vbx vbx

Done ;)