-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Document Release & Deploy Process #138
Comments
Thanks for creating this issue! Agreed this would be very helpful. Also could we maybe include a list of people who have deployment credentials so we know who to go to if there are production issues? Seems like this documentation is out of date: https://github.com/edgi-govdata-archiving/web-monitoring/blob/master/ARCHITECTURE.md#deployment-plan. Is this where you were planning on adding it? Otherwise perhaps it can be removed to avoid confusion. |
Oh geez, yeah, that’s super out of date. We’ve been running everything on AWS and mostly on Kubernetes for a while now. That might be the right place to put this stuff, but maybe it needs to be a separate doc. Haven’t thought it through — made this issue to dump a quick outline down before I forgot it. |
Added a PR to update the architecture doc in #140. |
The main goal here is to replace the README with something that actually gives an overview of the repo and how to approach it. The current README has been moved to a separate folder with Kubernetes setup information. (I haven’t attempted to change that tutorial at all otherwise.) This also renames the templates directory to kubernetes (hopefully that makes things more clear) and shoves the old README and associated setup files/scripts in kubernetes/0-setup-guide. The kubernetes/README.md file still needs to be written. This is a part of edgi-govdata-archiving/web-monitoring#138.
This is done! |
We need to actually document our release and deployment processes. We should:
Briefly describe them in this repo. (Projects have a(PR: Remove deployment plan from architecture overview #140) (Update: ultimately decided to just delete this info, since it’s too easy to get out of sync with web-monitoring-ops.)release
branch that auto-builds & publishes Docker images; we deploy them manually and store Kubernetes, etc. configs in -ops.)In -ops, explain:
manually-managed
folder)In code repos, explain how
release
branch works.The text was updated successfully, but these errors were encountered: