Local Deployment
Deploy OpenOps on your local machine
This guide explains how to install the OpenOps docker-compose release on a local machine. Note that these settings are for testing purposes only and not for a production environment.
Installing OpenOps automatically
Run the following command to install, configure and run OpenOps:
This script supports macOS, Ubuntu and Windows (via WSL2 Ubuntu).
Installing OpenOps manually
Alternatively, you can follow the manual installation steps provided below for your operating system.
On macOS
- Install Docker Desktop by following these instructions.
- Open a new terminal window and run the following command to create a folder and download the OpenOps release files:
- Open the
.env
file in the OpenOps installation folder. Change the values of the following variables that represent credentials. Do it now, as you won’t be able to change these values after the initial deployment:OPS_OPENOPS_ADMIN_EMAIL
: the email of your OpenOps installation’s root admin account.OPS_OPENOPS_ADMIN_PASSWORD
: the password of your OpenOps installation’s root admin account.OPS_POSTGRES_USERNAME
: the username of the Postgres database that OpenOps uses.OPS_POSTGRES_PASSWORD
: the password of the Postgres database that OpenOps uses.OPS_ANALYTICS_ADMIN_PASSWORD
: the password of the OpenOps Analytics admin account (the username is hardcoded toadmin
).
- Pull the images and run
docker compose
:If you face a rate limit while downloading, run the command again.
You can now access the application by navigating to http://localhost.
On Ubuntu Server
- During the Ubuntu Server installation, select Docker to be added to the installation. If you need to install Docker later, follow the instructions here.
- Log in to your server and run the following commands to create a folder and download the OpenOps release files:
- Identify your own IP address:
The output should look something like this:In this case, the IP address is
192.168.1.50
. - Open the
.env
file in the OpenOps installation folder. Change the values of the following variables that represent credentials. Do it now, as you won’t be able to change these values after the initial deployment:OPS_OPENOPS_ADMIN_EMAIL
: the email of your OpenOps installation’s root admin account.OPS_OPENOPS_ADMIN_PASSWORD
: the password of your OpenOps installation’s root admin account.OPS_POSTGRES_USERNAME
: the username of the Postgres database that OpenOps uses.OPS_POSTGRES_PASSWORD
: the password of the Postgres database that OpenOps uses.OPS_ANALYTICS_ADMIN_PASSWORD
: the password of the OpenOps Analytics admin account (the username is hardcoded toadmin
).
- In the
.env
file, find theOPS_PUBLIC_URL
variable and replace its value,http://localhost
, with the IP address that you’ve previously identified. In our example, the IP address would behttp://192.168.1.50
. - Pull the images and run
docker compose
:If you face a rate limit while downloading, run the command again.
On Windows (with PowerShell)
- Install Docker Desktop by following these instructions.
- Add a new folder for OpenOps in your PowerShell console:
- Download the OpenOps release files:
- Open the
.env
file in the OpenOps installation folder. Change the values of the following variables that represent credentials. Do it now, as you won’t be able to change these values after the initial deployment:OPS_OPENOPS_ADMIN_EMAIL
: the email of your OpenOps installation’s root admin account.OPS_OPENOPS_ADMIN_PASSWORD
: the password of your OpenOps installation’s root admin account.OPS_POSTGRES_USERNAME
: the username of the Postgres database that OpenOps uses.OPS_POSTGRES_PASSWORD
: the password of the Postgres database that OpenOps uses.OPS_ANALYTICS_ADMIN_PASSWORD
: the password of the OpenOps Analytics admin account (the username is hardcoded toadmin
).
- Run
docker compose
:If you face a rate limit while downloading, run the command again.
Updating OpenOps to a newer version
See Updating OpenOps.
Cloud templates
On localhost, cloud templates may not be able to load when using the Safari browser.
Configuring Slack approvals
If you would like to run a workflow that uses Slack approvals, please follow the steps:
- Download and create a free account in ngrok
- Start ngrok
- Copy the Forwarding address
- Go to the OpenOps installation directory
- Inside the directory, make a copy of the
.env.defaults
file and save it as.env
- Open the file and set OPS_PUBLIC_URL to the Forwarding address you copied in step 3
- Restart the containers
Using Azure CLI in workflows: running with local credentials
It is possible to share your local session with the platform for local applications.
To do this, you need to set two environment variables in the .env
file under the installation folder:
OPS_ENABLE_HOST_SESSION=true
: enables sharing of the host session with the platform container.HOST_AZURE_CONFIG_DIR="~/.azure"
: defines the path to the host machine’s Azure configuration folder that will be shared with the platform container.
Support
Feel free to join our Slack community if you have any questions or need help with the installation.