Skip to content

Commit

Permalink
build(other): test deployment locally
Browse files Browse the repository at this point in the history
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
2. `cd deployment/local-testing`
3. `vagrant up` .. and wait
4. Following services are running:
  * http://localhost:8080/
  * http://localhost:8080/api
  * http://localhost:8080/docs
5. Be amazed
  • Loading branch information
roschaefer committed Jun 27, 2024
1 parent 0a786fa commit 4883860
Show file tree
Hide file tree
Showing 4 changed files with 70 additions and 0 deletions.
1 change: 1 addition & 0 deletions deployment/local-testing/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
.vagrant
18 changes: 18 additions & 0 deletions deployment/local-testing/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Local test deployment

Currently, we're deploying to a vServer. The following will set up virtual machines locally in order to test out the deployment before it hits `staging` or `production`.

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:8080/>
- <http://localhost:8080/api>
- <http://localhost:8080/docs>

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.
14 changes: 14 additions & 0 deletions deployment/local-testing/Vagrantfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Defines our Vagrant environment
#
# -*- mode: ruby -*-
# vi: set ft=ruby :

image = "debian/buster64"

Vagrant.configure("2") do |config|
config.vm.box = 'generic/alpine319'
config.vm.provision :shell, path: "bootstrap.sh"
config.vm.network "forwarded_port", guest: 8080, host: 3000
config.vm.network "forwarded_port", guest: 80, host: 3001
config.vm.network "forwarded_port", guest: 8082, host: 3002
end
37 changes: 37 additions & 0 deletions deployment/local-testing/bootstrap.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
#!/bin/sh

apk update
apk upgrade
apk add nginx openrc nodejs npm git mysql mysql-client


npm install pm2 -g
pm2 startup

rc-update add pm2 boot

service mariadb setup
rc-update add mariadb boot
sed -e '/skip-networking/ s/^#*/#/' -i /etc/my.cnf.d/mariadb-server.cnf
service mariadb start


cd /var/www/localhost/htdocs/
git clone https://github.com/dreammall-earth/dreammall.earth.git
cd dreammall.earth

mkdir -p /etc/nginx/http.d
cp -f ./deployment/nginx/default.conf /etc/nginx/http.d/default.conf
cp ./deployment/nginx/frontend.conf /etc/nginx/http.d/frontend.conf
cp ./deployment/nginx/admin.conf /etc/nginx/http.d/admin.conf

service nginx restart

mysql -e "CREATE USER 'dreammall'@'localhost' IDENTIFIED BY 'SECRET'; GRANT ALL PRIVILEGES ON * . * TO 'dreammall'@'localhost'; FLUSH PRIVILEGES;"

cp backend/.env.dist backend/.env
cp presenter/.env.dist presenter/.env
cp frontend/.env.dist frontend/.env
cp admin/.env.dist admin/.env

deployment/deploy.sh

0 comments on commit 4883860

Please sign in to comment.