DevOps 2025

Project repository for group 'the happy group'

Environment variables and Vagrant

We are using a package called dotenv for managing environment variables. In order to install the package, run bundle install from your terminal.

We must never expose our .env file public, because it contains secrets. Therefore it is ignored in our .gitignore. All developers must have a .env file located in the root folder of our project. Information about how to set this up is shared elsewhere.

In order to be able to run vagrant commands, such as vagrant provision and vagrant rsync, you must have the following plugins installed to vagrant:

vagrant-digitalocean (0.9.6, global)
vagrant-env (0.0.3, global)
vagrant-reload (0.0.1, global)
vagrant-scp (0.5.9, global)

Ruby installation

Requires ruby version >= 3.4.1

Requires a bundle installation. Can be installed by running the following command

sudo gem install bundler

Before running the project, you will need to install all the dependencies from the Gemfile. Run bundle install from the terminal in order to do so.

Now you will be able to run the project from the terminal

bundle exec rackup src/minitwit/config.ru -p 4567

Testing

For testing you will need two libraries pytest and requests, these can be installed with pip:

pip install pytest requests

Secondly, you must have an environment variable ENV set to one of test, dev, prod Now with the website running as described above, you can simply run pytest

Docker

This assumes you have installed Docker on your computer.

In order to run the application in a docker container, run the following two commands

docker build -t thg/rubytwit:latest .
docker run --rm -p 4567:4567 thg/rubytwit

And you should be able to access the container at http://localhost:4567/public

Vagrant

This assumes you have a DigitalOcean account linked to your public SSH key and that you have created a API key in your account settings.

You also need to install Vagrant on your machine.

Install Vagrant DigitalOcean Plugin

vagrant plugin install vagrant-digitalocean

Change ssh path in Vagrantfile to your own ssh private key. (Make sure that you have setup ENV variables SSH_KEY_NAME, DIGITAL_OCEAN_TOKEN) Your .zshrc file should look like this:

export SSH_KEY_NAME="{YOUR_DIGITAL_OCEAN_KEYNAME}"
export DIGITAL_OCEAN_TOKEN="{YOUR_DICITAL_OCEAN_TOKEN}"

Run vagrant up to deploy a new version.

You can access the webserver and the restriced ip, which you can find inside your droplet settings in the Digital Ocean platform.