The Longhorn Containers
The repository is docker-okapi with currently 2 containers:
- combined (Longhorn 0.37 - 1.46)
- combined-java11 (Longhorn 1.46 - )
When a new Longhorn version appears, that needs a new Java-version, we will have to add more containers.
There is a pipeline-script in the repository that will build & push the containers to our docker-hub.
To add a version:
- Upload the Longhorn-*.war to our Cloud: "PROD: Shared Backup // Other Services" → "Other Services" => /var/www/webroot/downloads.translate5.net/. There is a Favorite in the Frontend of our Cloud in that Node. Customers expect to find a matching windows tools/apps download as well (add to /okapi-apps)
- Respect the naming-scheme as defined in application/modules/editor/Plugins/Okapi/README.md chapter "OKAPI Longhorn Versioning & Releasing"
- Add the version to the Dockerfile
- Add the new version to the healthcheck.sh
- Execute the Pipeline
Managing new Longhorn versions (official builds and snapshots)
- Each build we get and plan to use must be added to nextcloud/Developer/okapi
- PLEASE keep the naming scheme when adding stuff there There are seperate ZIPs for Longhorn, the Tools and the Tools for Windows
- Each build shall be tested locally first. To achieve this, add a local volume to your OKAPI container and add the longhorn war-file to /var/lib/jetty/webapps
- Afterwards it can be added to the container as described above. It can be pushed without worries as the supported OKAPI versions are managed within translate5
- When the container is pushed it can be tested on our dev-servers and by Stephan Bergmann locally
- IF a new Java-Version is required for a new version, contact Thomas Lauria or Axel Becher as we currently have no established path how to do this
- The ROLL-OUT of the new version is done in the translate5-code, please read application/modules/editor/Plugins/Okapi/README.md chapter "OKAPI Longhorn Versioning & Releasing"