Re: Best practices for directories in which to store stuff in production

Check out cookiecutter django github On Wed, Nov 9, 2016 at 7:49 PM, Vijay Khemlani wrote: > I prefer to keep everything in /home (at least the virtualenv, project > code, settings and logs), that way you don't need special permissions to > modify those files and it is more or less separated fro

Re: Best practices for directories in which to store stuff in production

I prefer to keep everything in /home (at least the virtualenv, project code, settings and logs), that way you don't need special permissions to modify those files and it is more or less separated from the system files. static and media files in Amazon S3 Caching... I used memcached, so I have no

Re: Best practices for directories in which to store stuff in production

If I had to use such scheme, I would put the django application in a package for the target system. Like a .deb file for exemple. If your primary way of deploying is a git push from test/QA to production, split directory will cause plenty of headaches. Also, with an installation like this, I would

Best practices for directories in which to store stuff in production

Hello, I was thinking about using this scheme: /usr/local/lib/projectname Program files (i.e. repository) /usr/local/lib/projectname-virtualenv Virtualenv /var/lib/projectname/media Media files /var/cache/projectname/static Static files, collected with collectstati