http://localhost:8080
.appengine/src/greenday_core/settings/local.py
based on appengine/src/greenday_core/settings/local.py.sample
and fill the API keys as per above.appengine/src/greenday_core/settings/test.py
based on appengine/src/greenday_core/settings/test.py.sample
and fill the API keys as per above.docker-compose build
docker-compose up
docker-compose exec montage grunt build
docker-compose exec montage bash
to get inside the running container. The Python virtual environment is automatically activated for you.
python bin/manage.py shell
and other Python / Django commands are availablenpm run test:backend
to run backend testsgrunt watch
to watch code changes in JavaScript / HTML and rebuild the packagenpm run test:frontend
to run unit testsAll connections to the Cloud SQL instances are made over SSL. You will need to set yourself up with a private key to access this.
client-key.pem
, client-cert.pem
and ca-cert.pem
(this is named server-ca
when you download it from the console. You will need to rename it to ca-cert.pm
when you store it locally) and save them in {project root}/keys/(qa|live)/
../bin/manage.py dbshell --settings=greenday_core.settings.(qa|live)
QA should mirror the develop
branch. QA has a fixed version, called "qa".
appengine/auth.json.example
to appengine/auth.json
npm run full-deploy-qa
PS: At Meedan, a deployment to QA happens automatically when a push happens to develop
. You can also call it from Jenkins (job montage-develop
) or from Slack using Hubot: @hu deploy-montage-qa
.
Live should mirror the master
branch.
VERSION
appengine/auth.json.example
to appengine/auth.json
npm run full-deploy-live
PS: At Meedan, you can deploy from Jenkins (job montage-master
) or from Slack using Hubot: @hu deploy-montage-live
.