Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Bst dev server deploy configuration #422

Merged
merged 4 commits into from
Dec 21, 2017
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
23 changes: 23 additions & 0 deletions circle.yml
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,26 @@ deployment:
--restart=always
-P bespoken/bst:$CIRCLE_TAG
- ./hyper fip attach -f 199.245.58.242 bst

bst-dev-server:
tag: /bst-dev-.*/
commands:
- docker login -e $DOCKER_EMAIL -u $DOCKER_USER -p $DOCKER_PASS
- docker build -f docker/Dockerfile -t bespoken/bst-dev:$CIRCLE_TAG .
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep the image name the same (bespoken/bst) - and use the tag to differentiate it (bst-dev-x or bst-server-dev-x). If you look in DockerHub, that is a cleaner way to organize images.

- docker push bespoken/bst-dev:$CIRCLE_TAG
- ./hyper config --accesskey $HYPER_KEY --secretkey $HYPER_SECRET --default-region us-west-1
- ./hyper login -e $DOCKER_EMAIL -u $DOCKER_USER -p $DOCKER_PASS
- ./hyper pull bespoken/bst-dev:$CIRCLE_TAG
- ./hyper rm -f bst-dev || true
- >
./hyper run
-e AWS_ACCESS_KEY_ID=$PROD_AWS_ACCESS_KEY_ID
-e AWS_SECRET_ACCESS_KEY=$PROD_AWS_SECRET_ACCESS_KEY
-e SSL_CERT="$SSL_CERT"
-e SSL_KEY="$SSL_KEY"
-d
--name bst-dev
--size s4
--restart=always
-P bespoken/bst-dev:$CIRCLE_TAG
- ./hyper fip attach -f 199.245.58.199 bst-dev