Thanks Ben. Do you have recommendation as to where I should store static media files so later when I make changes and "redeploy" the website, the past contents (i.e: blog feature images) won't get deleted? From my research I think aws s3 stands out the most and it seems possible to store the media files on the same server as the website, too?
On Sunday, July 10, 2016 at 12:22:04 AM UTC-5, Ben Havilland wrote: > > Hi Tran, the issue with doing this is that in any scalable environment > you'll lose your files when nodes spin up/down. Media should be added > after deployment, via upload. If you want the file to be persistent then > you can put it in static (not media) files, do a `python manage.py > collectstatic`. Static files can be added on your local server. Media > files are volatile and should live elsewhere. Hope that helps. Ben > > On Sat, Jul 9, 2016 at 5:01 PM, Tran <[email protected] <javascript:>> > wrote: > >> I am using blog with feature image enabled. Whenever I deploy the >> application, the feature image that I uploaded disappear. I think the >> reason is because I don't have the right setup for the static media (I plan >> to use the same server, not aws). Before I add the new change to the local >> files, I do git pull (which always says the folder is up to date even >> though I uploaded the img on the server). Anybody knows a good way to >> correctly set up static media on the same server? Thanks >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
