Notes

This application has been a place for me to learn Docker, Django, mapping, and ETL. The following are some notes from that.

helpful docker commands

run django manage commands

docker-compose run --rm backend python3 manage.py shell

rebuild image after changes to react package.json or django requirements.txt, environment variables, etc:

$ docker-compose up --build

to run both at once:

$ docker-compose up

to run only frontend:

$ docker run -it -v $PWD/frontend:/app -p 3000:3000 frontend:latest npm start

to run only backend:

$ docker run -v $PWD/backend:/app/backend -p 8000:8000 backend:latest

to create a new app module:

$ docker-compose run --rm backend python3 manage.py startapp app_name

for example, to add axios, go:

$ docker-compose run --rm frontend npm add axios
$ docker-compose down
$ docker-compose up --build

Run migrations for Django in dev:

$ docker-compose exec web python manage.py migrate --noinput

If you're ever doing anything with docker-compose volumes and it don't work:

docker-compose down -v # removes volumes

$docker-compose logs -f

docker-compose run --rm backend python3 manage.py shell

docker-compose run --rm backend python manage.py dumpdata --exclude=sessions --exclude=messages --exclude=contenttypes --exclude=auth.permission --indent 2 > backend/app/fixtures/db.json

docker-compose run --rm backend python manage.py loaddata app/fixtures/db.json

run tests
docker-compose run --rm backend python3 manage.py test

debug a container or stop it

$ docker ps # get the id of the running container
$ docker stop <container> # kill it (gracefully)

Since we're changing project settings, we'll need to stop our Docker Compose processes (either ctl+c or docker-compose stop in a separate tab) and start it again with docker-compose up. docker-compose down works to stop too