On Wed, Feb 10, 2016 at 7:15 AM, Fred Stluka <[email protected]> wrote:
> On 2/10/16 4:37 AM, James Schneider wrote: > > ... make sure that the Apache system user has read access to that > directory and all subdirectories, and no write access ... > > James, > > Won't that prevent Django from creating *.pyc files from the > deployed *.py files? Or do you suggest deploying *.pyc files? > > --Fred > Oh, yep, you're right. It was 1:30am and I was in PHP mode in my head (I'm not getting kicked off the list for mentioning that word, right? ;-D). I believe that means that the Apache user needs write access to the project folders (to create the .pyc files), but still only needs read access to the .py files. I believe that you can tweak the write access to the .pyc files and parent folders after they have been generated by mod_wsgi/Apache. You can also do a deployment just using just the .pyc files, if I remember correctly. Thanks for the double-check. -James -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciUx1pYvhL1HoAL1gU9Hrjn_C8V_SX73Si21WR8XZ4qM%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
