Closed S-Stephen closed 8 years ago
Looks broadly OK to me although I'd like the setup_mws3.py
somewhere other than top-level. Perhaps a deploy
directory?
Since the MWS3-specific WSGI script exists, you might as well get it to specify a MWS-specific settings.py
like the following:
from edpcmentoring.settings import *
# Perform any MWS-specific overrides here
SECRET_KEY=# ... etc, etc
This avoids the try:
/except NameError:
dance in settings.py
which is a little convoluted.
I hope to action the pythonish stuff next week
Now it's fairly self-contained I'm happy to merge as is and let style improvements in setup_mws3.py happen in a separate PR.
I've added a Python script to help the installation of the application onto the university's MWS3 service.
Included the import of a settings_local file (not to be checked in) in the settings.py
Produced a requirements.txt file for the MWS3 service
I imagine that this script needs moving into a script directory or similar at some point. The script;
installs a virtual env installs the required dependencies produces the .htacces file copies the wsgi.py file into position and produces a settings_local.py file
For some reason the application will not run without DEBUG=True (settings_local.py file). This obviously needs fixing but I've been unable to resolve atm