# Development Environments We have two instances which are automatically deployed using GitLab: - **dashboard.aura.radio** - Developer/Testing instance holding the latest codebase of the `main` branches. - **demo.aura.radio** - Demo instance with a stable release, based on a release tag configured in GitLab. ## Latest development instance (dashboard.aura.radio) We use the [gitlab-ci](https://gitlab.servus.at/aura/aura/-/blob/main/.gitlab-ci.yml) for Deploying specific versions of aura. - You Can adjust the Container versions at [gitlab-ci](https://gitlab.servus.at/aura/aura/-/blob/main/.gitlab-ci.yml#L44) ```properties AURA_STEERING_VERSION: "main" AURA_BATTERY_VERSION: "main" AURA_DASHBOARD_VERSION: "main" AURA_DASHBOARD_CLOCK_VERSION: "main" ... ``` - Choose between Docker Registry or Gitlab-Registry at [gitlab-ci](https://gitlab.servus.at/aura/aura/-/blob/main/.gitlab-ci.yml#L49) - `DOCKER_REGISTRY: "docker"` for Docker hub - `DOCKER_REGISTRY: "gitlab"`for Gitlab registry After committing your desired changes, Gitlab auto-deploys this version. Note, that the Pipeline will only run on protected branches. ## Latest release instance (demo.aura.radio) When a new _Tagged Release_ is published, Gitlab can be used to deploy this release by running some _manual deployment step_. To start deployment of a release go to _aura > Jobs_ and filter for jobs with the status "Manual". List of manual jobs Now click on the release job you want to deploy. Manual job item Simply click the button "Run" to deploy the release. Manual job deploy UI ## Auto Deployment based on feature branches While this is currently not used, the Auto Deployment feature also provides custom builds based on feature branches. For all components, feature branches automatically build Docker containers and push them to the [gitlab-registry](https://gitlab.servus.at/groups/aura/-/container_registries). To roll out new features, the [Compose-File](https://gitlab.servus.at/aura/aura/-/blob/main/config/aura-web/docker-compose.auto-deployment.yml), must be set to the corresponding tag of the feature branch. After the commit, the version will be rolled out automatically.