Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs and Makefile to reflect Fargate deploy #59

Merged
merged 1 commit into from Jan 29, 2019
Merged

Update docs and Makefile to reflect Fargate deploy #59

merged 1 commit into from Jan 29, 2019

Conversation

gravesm
Copy link

@gravesm gravesm commented Jan 29, 2019

This updates the documents for the current Fargate deployment process.
The Makefile has also been modified to account for the production
deployment. Actually promoting the staging build to production will
require (minimal) manual intervention.

This updates the documents for the current Fargate deployment process.
The Makefile has also been modified to account for the production
deployment. Actually promoting the staging build to production will
require (minimal) manual intervention.
1. Make your changes.
2. Run ``make dist`` from project root.
3. Test your changes by running ``docker run --rm carbon <carbon args>``, with ``<carbon args>`` being whatever arguments you would normally use to run carbon.

Copy link
Member

Choose a reason for hiding this comment

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

I can't comment on the bit I want to because it's not in this changes... under Building it mentions:
Running ``make dist`` creates a new container that is tagged as ``carbon:latest``. is that still accurate?

Copy link
Author

Choose a reason for hiding this comment

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

Yeah


When you are ready to deploy the current staging build to production, simply run::

$ make promote
Copy link
Member

Choose a reason for hiding this comment

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

🌈

Copy link
Member

@JPrevost JPrevost left a comment

Choose a reason for hiding this comment

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

If this works it's seems fine and makes sense to me at a high level.

@gravesm gravesm merged commit fbbc80e into master Jan 29, 2019
@gravesm gravesm deleted the docs branch January 29, 2019 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants