Could not import setuptools which is required to install from a source distribution.
Traceback (most recent call last):
File "/Users/dpage/.virtualenvs/pgaweb/lib/python2.7/site-packages/pip/req/req_install.py", line 387, in setup_py
import setuptools # noqa
File "/Users/dpage/.virtualenvs/pgaweb/lib/python2.7/site-packages/setuptools/__init__.py", line 10, in <module>
from six.moves import filter, map
ImportError: No module named six.moves
Perhaps the entire dependency tree should be added to requirements.txt?
What version of pip runs in your pyenv? We're able to pip install requirements inside a new 2.7.10 virtualenv, that gets created with pip 9.0.1 by default.
Apologies - my virtual env was messed up.
- Scripts to yarn to compile the SCSS and run the application
- Add startapp.sh script to start the application
The application runs under uWSGI - it's not going to be started via a script. It's auto-updated periodically from git, and uWSGI will restart when necessary so if any pre-processing of files is required, that needs to be done at startup automatically.
Okay, so it sounds like shelling out to yarn in wsgi would resolve this.
I think your suggestion below would be cleaner.
Otherwise, what does the auto-update process look like? perhaps compilation steps belong there rather than in app startup.
It's really just a GIT pull. uWSGI then detects the change and restarts that app. We could certainly have it do "git pull && yarn install && yarn run scss" or similar.
Now that said, the scss doesn't actually seem to build for me. I had to make 2 changes to get anywhere:
2) Remove the STATIC_ROOT directive from settings.py (so it didn't try to compile to /static) and replace with COMPRESS_ROOT='static/' and SASS_PROCESSOR_ROOT='static/'.
That left me with a running site, that seems to behave as expected, at least when run standalone.