- vim ADSDeploy/local_config.py #edit, edit
vagrant up db rabbitmq app --provider=docker
vagrant ssh app
cd /vagrant
This will start the pipeline inside the app
container - make sure you have configured endpoints and
access tokens correctly.
We are using 'docker' provider (ie. instead of virtualbox VM, you run the processes in docker).
On some systems, it is necessary to do: export VAGRANT_DEFAULT_PROVIDER=docker
or always
specify `--provider docker' when you run vagrant.
The directory is synced to /vagrant/ on the guest.
If you (also) hate when stuff is unnecessarily complicated, then you can run/develop locally (using whatever editor/IDE/debugger you like)
- virtualenv python
- source python/bin/activate
- pip install -r requirements.txt
- pip install -r dev-requirements.txt
- vagrant
up db rabbitmq --provider=docker
This will setup python virtualenv
and the database + rabbitmq. You can run the pipeline and
tests locally.
vagrant up rabbitmq
The RabbitMQ will be on localhost:6672. The administrative interface on localhost:25672.
vagrant up db
PostgreSQL on localhost:6432
vagrant up prod
It will automatically download/install the latest release from the github (no, not your local changes - only from github).
If you /ADSDeploy/prod_config.py is available, it will copy and use it in place of
local_config.py
No ports are exposed, no SSH access is possible. New releases will deployed automatically.
Typical installation:
vim ADSDeploy/prod_config.py
# edit, edit...vagrant up prod
- cd manifests/production/app
- docker build --name ADSDeploy -t ADSDeploy .
- cd ../../..
- vim prod_config.py # edit, edit...
- dockerun -d -v .:/vagrant/ --name ADSDeploy ADSDeploy /sbin/my_init
Here are some useful commands:
-
restart service
docker exec ADSDeploy sv restart app
-
tail log from one of the workers
docker exec ADSDeploy tail -f /app/logs/ClaimsImporter.log
develop