bulbil / vagrant-nginx-django Goto Github PK

Takes https://github.com/michaelck/puppet-lamp-stack-for-omeka and makes it stupider -- only shell provisioning so far.

Relied on the following online tutorials:

• Django Applications with uWSGI and Nginx, Justin Ellingwood
• Setting up Nginx + Django + uWSGI, Richard O'Dwyer
• uWSGI's readthedocs on Setting up Django and your web server with uWSGI and nginx

• This setup relies on a few assumptions:
  • uWSGI is pip-installed globally while all other packages are pip-installed into virtualenvs
  • Python3 configuration: echo "export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
  • echo "export WORKON_HOME=~/venvs" >> ~/.bashrc
  • echo "source /usr/local/bin/virtualenvwrapper.sh" >> ~/.bashrc
  • YOU CANT USE PYTHON 3 unless uwsgi for python 3 installed globally! (hard won knowledge)
  • (maybe try python3 -m pip install uwsgi in bootstrap.sh instead)
• Remove link to default in etc/nginx/sites-enabled/default
• Unless specifically configured, Vagrantfile only points traffic from guest port 80 -- so any debugging using other ports won't forward

Configure PostgreSQL

• createdb <name> & createuser -P
• psql
• grant privileges ...
• you may have to change etc/postgresql/<version>/main/pg_hba.conf to except md5 authentication

Configure virtualenvwrapper + Django project

• mkvirtualenv --no-site-packages -i django -i psycopg2 -i django-bootstrap3 -p python3 <project>
• cd /srv/apps/<project> & django-admin.py startproject <project> [existing path]
• mkdir /srv/apps/<project>/static
• settings.py
  • 17:STATIC_ROOT=os.path.join(BASE_DIR,'static')
  • not all INSTALLED_APPS necessary -- delete any before running migrate
  • change DATABASE settings:

        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'NAME': '<db>',
        'USER': '<user>',
        'PASSWORD': '<pw>',
        'HOST': 'localhost',
        'PORT': '',

• ./manage.py migrate
• ./manage.py collectstatic
• if using ./manage.py runserver don't forget 0.0.0.0:8000 (quirk of how 127.0.0.1 "loops back" -- or something)

• to deal with the issue of characters that are not conventionally supported by existing unicode hex, loaded a Navajo web font
• [source font[(http://www.lapahie.com/Fonts/Navajo_Fonts_Windows/Century_Gothic_Navajo/CENTGN__.TTF)
• font generator
• or, possibly a way simpler solution, language geek's keyboard