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. Wykonuje ono kilka rzeczy:
git pull wczytuje zaktualizowany kod z repozytorium git. Jeśli wystąpią konflikty, może być konieczne wykonanie git pull oddzielnie i rozwiązanie konfliktów przez ponownym wypróbowaniem skryptu ./bw-dev update.docker-compose build ponownie kompiluje obrazy, co zapewnia zainstalowanie odpowiednich pakietów. This step takes a long time and is only needed when the dependencies (including pip requirements.txt packages) 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 migrate runs the database migrations in Django using the newly built Docker imagesdocker-compose run --rm web python manage.py collectstatic --no-input loads any updated static files (such as the JavaScript and CSS)docker-compose down; docker-compose up -d will 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