docker-compose run --rm otp otp --build /var/otp
in the deployment/graph directory.deployment/ansible/group_vars/development_template
to deployment/ansible/group_vars/development
src/
folder and run npm install
to install the node modules on the host machinevagrant up
. You can choose to change the Virtualbox shared folder type for the app
VM from its default NFS by:
CAC_APP_SHARED_FOLDER_TYPE=virtualbox vagrant up
./scripts/serve-js-dev.sh
on the host will rebuild the front-end app on file change (the browser must be reloaded manually to pick up the change). Alternatively, cd /opt/app/src && npm run gulp-development
can be run manually in the VM to pick up changes to the static files.Note that if there is an existing build Graph.obj in otp_data
, vagrant provisioning in development mode will not attempt to rebuild the graph, but will use the one already present.
Django migrations are run as part of app provisioning, here, but there may be instances where you need to manually run migrations outside of provisioning, in which case use the command:
vagrant ssh app -c 'cd /opt/app/python/cac_tripplanner && python3 manage.py migrate'
aws configure --profile gophillygo
if you haven't alreadyotp
machine, make sure the latest GTFS are in otp_data
, then build a graph when them in the development environment provisioning. This will result in a new Graph.obj
file being written to otp_data
.python3 -m venv .venv && source .venv/bin/activate && pip install -r python/cac_tripplanner/deployment_requirements.txt
AWS_PROFILE=gophillygo deployment/cac-stack.py create-ami
--machine-type
parameter, which may be set to one of: bastion
, otp
, or app
.deployment/default_template.yaml
to deployment/default.yaml
and edit variablesaws configure --profile gophillygo
if you haven't alreadyBlue
stacks in the Production
environment, run: AWS_PROFILE=gophillygo deployment/cac-stack.py launch-stacks --stack-color blue --stack-type prod
VPC
stack is up in Production -- it will be launched if it isn't already runningDataPlane
stack is up in Production -- it will be launched if it isn't already runningOtpServer
Blue stack is up in Production -- it will be launched if it isn't already runningWebServer
Blue stack is up in Production -- it will be launched if it isn't already runningGreen
), will use the same VPC
and DataPlane
stacks, but will create different OtpServer
and WebServer
stacks (if they don't already exist).otp_host
in production group_vars to the CloudFront distribution with the desired color.create_ami
command to build new AMIs.default.yaml
with new AMI ids.launch_stacks
command to launch stacks with the desired color.WebServer
ELB DNS.