Unee-T

• How to test with Bugzilla in a local environment
• ECS deploy with ./deploy.sh

Environment variables

They are securely managed in AWS's parameter store. The variables are retrieved via an environment setup script, which is utilised by deploy.sh.

Deployment

Happens automatically on master on the development AWS account 8126-4485-3088 with AWS_PROFILE uneet-dev. Travis CI deployments made via pull request will fail since it will not have access to AWS_SECRET_ACCESS_KEY.

Production deployment on AWS account 1924-5899-3663 is done manually via ./deploy.sh -p via the AWS_PROFILE aws-prod.

Logs

Frontend logs to the meteor log group in CloudWatch, which is controlled by the compose file.

Meteor builds

The canonical master branch CI build location is https://unee-t-media.s3-accelerate.amazonaws.com/frontend/master.tar.gz

To discover other branches:

aws --profile uneet-dev s3 ls s3://unee-t-media/frontend/

Every commit is also uploaded to:

aws --profile uneet-dev s3 ls s3://unee-t-media/frontend/commit

Commits are expired after 90 days

Setup

1. Install Meteor https://www.meteor.com/install

2. Install dependencies

npm install

Start App

npm start