Commit 79c1c886 authored by Walter Heck's avatar Walter Heck

Update scenario.md

parent f8069096
......@@ -6,7 +6,7 @@ In short, there are three different ways to deploy OpsTheater, each with their o
Usecase: you want to help in developing OpsTheater further. In this scenario, you don't plan to ever run any of the deployment in production. You are okay to use local virtualbox and vagrant in order to give you maximum flexibility in bringing up and tearing down vm's. Some instructions can be found here:
https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.7/deployment/development.md
<https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/2.0/deployment/development.md>
## Scenario 2: OpsTheater deployment for non-production
......@@ -19,4 +19,4 @@ Usecase: in this scenario you want to explore OpsTheater and see what it is all
Usecase: in this scenario you are planning a (new) production environment and need to make careful choices that fit for your architecture and your usecase. In this scenario we can't do the deployment in an automated fashion, so expect lots of planning work.
Read more:
https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.7/deployment/production.md
https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/2.0/deployment/production.md
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment