Skip to content
This repository has been archived by the owner on May 2, 2023. It is now read-only.

How to start

Paul Werther edited this page Jun 30, 2021 · 4 revisions

To avoid compatibility and dependency issues, and to make it easy to set up, we use Docker. You can build your own images or use prebuilt ones from Docker Hub.

Prebuild docker images

Use the docker-compose.yml from the docker/envizon_prod directory and run it with docker-compose up -d.

The Docker image will be pulled from evait/envizon.

If you want to update the app image or pull it manually, you can do so with docker pull evait/envizon.

If you want to provide your own SSL-certificates, modify the docker-compose.yml according to your needs, otherwise they will be generated.

For the lazy ones

mkdir envizon
cd envizon
wget https://raw.githubusercontent.com/evait-security/envizon/master/docker/envizon_prod/docker-compose.yml
echo SECRET_KEY_BASE="$(echo $(openssl rand -hex 64) | tr -d '\n')" > .envizon_secret.env
sudo docker-compose up -d

Running from local git checkout

git clone https://github.com/evait-security/envizon
cd envizon/docker/envizon_local
echo SECRET_KEY_BASE="$(echo $(openssl rand -hex 64) | tr -d '\n')" > .envizon_secret.env
sudo docker-compose up

Development

If, for whatever reason, you want to run the development environment in production, you should probably consider changing the secrets in config/secrets.yml, and maybe even manually activate SSL.

git clone https://github.com/evait-security/envizon
cd envizon/docker/envizon_dev
sudo docker-compose up
Clone this wiki locally