When there are changes available in the production branch, you can install and get them running on your instance using the command
./bw-dev update. This does a number of things:
git pullgets the updated code from the git repository. If there are conflicts, you may need to run
git pullseparately and resolve the conflicts before trying the
./bw-dev updatescript again.
docker-compose buildrebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip
requirements.txtpackages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
docker-compose run --rm web python manage.py migrateruns the database migrations in Django using the newly built Docker images
docker-compose run --rm web python manage.py compile_themescompiles the BookWyrm themes
docker-compose down; docker-compose up -dwill restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
./bw-dev populate_streams # Or use docker-compose directly docker-compose run --rm web python manage.py populate_streams
If something has gone terribly awry, the stream data can be deleted.
docker-compose run --rm web python manage.py erase_streams