Closed cuducos closed 6 years ago
I think that a good way to test it, is by running the tests.
What I did:
Checked out to this branch:
$ git fetch origin
$ git checkout -b cuducos-production-fixes origin/cuducos-production-fixes
$ git merge master
Run the tests:
$ docker-compose run --rm django python manage.py test --parallel
The result:
➜ jarbas git:(cuducos-production-fixes) ✗ docker-compose run --rm django python manage.py test --parallel
Starting jarbas_postgres_1 ...
Starting jarbas_queue_1 ...
Starting jarbas_postgres_1 ... done
Starting jarbas_tasks_1 ... done
Creating test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
System check identified no issues (0 silenced).
...........................................................................................................................................................................
----------------------------------------------------------------------
Ran 171 tests in 5.180s
OK Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'...
What is the purpose of this Pull Request?
Testing the new production architecture with Docker, using the new domain, I made some minor changes to make it happen.
What was done to achieve this purpose?
django
containerjarbas.serenatadeamor.org
tojarbas.serenata.ai
nginx
andnginx.docker
anymore, justnginx.conf
)VIRTUAL_HOST_WEB
envvarHow to test if it really works?
Access
jarbas.serenata.ai
and check if it's working (it uses this branch, notmaster
).Who can help reviewing it?
@anaschwendler