oCIS instance for the oCIS Team

ocis.team.owncloud.works provides a permanent testing instance for the oCIS team.

This instances is needed besides our continuously deployed testing instances for a few reasons:

• These instances are publicly available since they are using our demo accounts. Therefore we need to prune them on a daily basis to prevent misuse. But this also prevents usage on a normal basis (like pointing a desktop client to it).
• These instances are automatically deployed and no checks happen if everything is still working.

Besides the reasons mentioned above, this instances also fulfills these purposes:

• It will be administered like a production instance and therefore we need apply migrations during updates, if needed.
• See how it scales and adapt the deployment on arising needs.
• Document how this instance evolved (see setup history below)

Users have to apply manually for an account in our chat.

Setup history

Initial (current) setup

Currently our oCIS instance uses a slight modification of our oCIS with Keycloak deployment example.

Differences to the deployment examples:

• Manual Keycloak configuration is applied (therefore no demo users are available)
• Secrets are not stored in the git repository
• Docker image versions are pinned (version and digest-pinning)
• Data of oCIS and the Keycloak PostgreSQL database are not stored in docker volumes on local disc but on a Hetzner cloud block storage mount, which can be easily grown

Diary

• 02/18/2021 initial deployment of oCIS 1.2.0

• 02/22/2021 fix sharing

• 02/22/2021 theming of login page

• 02/23/2021 theming of account settings

• 02/23/2021 start onboarding of users

• 03/10/2021 update to oCIS 1.3.0: no breaking changes, dead simple update

  • bump oCIS version
  • run a git pull and docker-compose up -d on the server

• 03/31/2021 update to oCIS 1.4.0 available: breaking changes, oCIS data needs to be pruned

• 04/09/2021 schedule update date and notify users that they need to back up their data

• 04/14/2021 update to oCIS 1.4.0

  • stop oCIS by running docker-compose down
  • backup oCIS storage location and prune the original storage location
  • bump oCIS version
  • run a git pull and docker-compose up -d on the server
  • notify users that they can reupload their data and recreate shares

• 04/23/2021 update to oCIS 1.5.0: no breaking changes, dead simple update

  • bump oCIS version
  • run a git pull and docker-compose up -d on the server

• 05/10/2021 update to Keycloak 13.0.0: no breaking changes, dead simple update

  • bump Keycloak version
  • run a git pull and docker-compose up -d on the server

• 04/23/2021 reverted update to oCIS 1.6.0: breaking changes detected during update

  • bump oCIS version
  • run a git pull and docker-compose up -d on the server
  • noticed two breaking changes: 1 and 2
  • revert bump oCIS version
  • run a git pull and docker-compose up -d on the server

• 05/26/2021 changed internal transport from https to http

• 06/08/2021 schedule update date and notify users that they need to back up their data

• 06/10/2021 update to oCIS 1.7.0

  • stop oCIS by running docker-compose down
  • backup oCIS storage location and prune the original storage location (because of breaking changes from oCIS 1.5.0 to 1.6.0)
  • bump oCIS version
  • run a git pull and docker-compose up -d on the server
  • notify users that they can reupload their data and recreate shares