build(other): test deployment locally #1272
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
from
a21eab7 to
cfda16b
Compare
roschaefer
changed the title
roschaefer
commented
Jun 27, 2024
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
from
cfda16b to
3f91cc8
Compare
roschaefer
commented
Jun 27, 2024
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
3 times, most recently
from
eb62856 to
4883860
Compare
roschaefer
commented
Jun 27, 2024
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
from
4883860 to
385e4cb
Compare
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
from
385e4cb to
f07d575
Compare
Context ------- There was a similar PR #1263 attempting to do the same with docker. I was running into isolation issues with docker (setting hostname not allowed in the container and some system folders are read-only) and learned that for this use case, an actual hypervisor would be better and vagrant is a conventional tool to set up these virtual machines. Motivation ---------- On the weekend we had a downtime on production because `nginx` configurations got out of sync with the code in newer releases. To prevent this and further downtimes I suggest to check in our deployment configuration and make it *reproducible*. This PR is an attempt to create a virtual machine that behaves as similar as possible to production and can be used as a sandbox for changes to our deployment configuration. How to test ----------- 1. Install [Vagrant](https://www.vagrantup.com/) on your machine 1. `cd deployment/local-testing` 1. `vagrant up` .. and wait 1. Following services are running: - <http://localhost:8000/> - <http://localhost:8000/api> - <http://localhost:8000/docs> - <http://localhost:8080/> - <http://localhost:8082/> 1. Be amazed In the future we might want to use [Ansible](https://www.ansible.com/) for provisioning. We could run our playbooks against this virtual machine, too.
roschaefer
force-pushed
the
reproducable-deployment-with-vagrant
branch
from
f07d575 to
57c0102
Compare
Elweyn
approved these changes
Jul 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
There was a similar PR #1263 attempting to do the same with docker. I was running into isolation issues with docker (setting hostname not allowed in the container and some system folders are read-only) and learned that for this use case, an actual hypervisor would be better and vagrant is a conventional tool to set up these virtual machines.
Motivation
On the weekend we had a downtime on production because
nginxconfigurations got out of sync with the code in newer releases.To prevent this and further downtimes I suggest to check in our deployment configuration and make it reproducible.
This PR is an attempt to create a virtual machine that behaves as similar as possible to production and can be used as a sandbox for changes to our deployment configuration.
How to test
Install Vagrant on your machine
cd deployment/local-testingvagrant up.. and waitFollowing services are running:
Be amazed
In the future we might want to use Ansible for provisioning. We could run our playbooks against this virtual machine, too.