If you're reading this, you're reading the README.
- Base
- Specify role with
DJANGO_SETTINGS_MODULE
, e.g.dev.py
- Move manual setup to Python script (or better, to Docker!)
- Move app templates to base templates directory
- Send error emails
- Specify role with
- WineApp
- Add tests for logged-in user wine recommendations
- Add more wines, populate metadata with the usual junk
- Serve uploaded wine images with S3/CloudFront
- Add 'blog archive' thing for older Shouts & Murmurs posts
- Shrink larger images, use one-column layout for xs viewports
- Initialize virtualenv
python3 -m virtualenv .venv
- Activate venv
. .venv/bin/activate
- Install Python requirements
pip3 install -r requirements.txt
- Install apt requirements
xargs -a apt-requirements.txt sudo apt-get install
- Create Postgres user and database
sudo -u postgres psql
CREATE USER djangalex WITH PASSWORD 'hunter2';
(replacehunter2
if you dare)CREATE DATABASE djangalex OWNER djangalex;
\q
- Add secrets to env vars
- (this is another good candidate for moving to Docker, or at least
.bashrc
) export DATABASE_URL=postgres://djangalex:hunter2@localhost:5432/djangalex
export SECRET_KEY=hunter2
(or a somewhat more secure password, for you Krebs readers out there)export DEBUG=True
export AWS_STORAGE_BUCKET_NAME=foo
export AWS_ACCESS_KEY_ID=bar
export AWS_SECRET_ACCESS_KEY=baz
export DJANGO_SECRET_KEY=baz
- (this is another good candidate for moving to Docker, or at least
- Run initial database migration
./manage.py migrate
- Create superuser
./manage.py createsuperuser
- Run server!
./manage.py runserver
- Site should be accessible at
localhost:8000/
- Install Heroku CLI
sudo snap install --classic heroku
- Set Heroku env vars, if necessary
- Can be done from Heroku GUI or
heroku config:set FOO=bar
- Can be done from Heroku GUI or
- Do the jawn!
git push heroku master