Skip to content

OpenRMF OSS v1.9.0

Compare
Choose a tag to compare
@Cingulara Cingulara released this 11 Mar 17:14
· 22 commits to master since this release
d926e24

Updates in this v1.9.0 release:

  • Update to the latest NGINX Unprivileged web container
  • Update the base containers to Alpine Linux 3.17.2
  • Update to the latest DISA Templates as of March 9, 2023
  • Fix a bug on filtering hostnames case insensitive to host
  • Update to using Keycloak 20.0.3
  • Update configuration to run all under 1 NGINX port (breaking change with Keycloak 20)
  • Updated documentation for setup, install, min requirements, HTTPS

If you are upgrading, stop the current OpenRMF® OSS stack. Then unzip the contents of the OpenRMF ZIP file into the folder you are currently using and overwrite the YML and other script files.

I upgrading, be careful on the .env as you will have one setup for your environment.

Relaunch the OpenRMF stack and clear your browser cache. Then everyone will have to setup Keycloak as directed in the step-by-step instructions below. Keycloak 20 was put under the single docker-compose.yml file and it has to be setup again with the setup scripts. Then add back the users / assign roles as required.

Step-by-Step Instructions Everyone Must Read and Apply

https://github.com/Cingulara/openrmf-docs/blob/master/step-by-step.md use these once you download the ZIP into its own folder. Note that for those upgrading, v1.9 moves Keycloak under a single docker-compose.yml for a single port. The instructions are in this document.

IMPORTANT: You must look at the .env file to set the Keycloak/OpenID location and realm. Check the .env file in the OpenRMF folder you unzip to set the IP address correctly. The docker-compose stack YML files read that .env file to launch. These cannot be "localhost" or "127.0.0.1" as inside a docker container those mean that container, not the host it is running on.

This release is for AMD or Intel based 64-bit operating systems and machines. ARM machines such as Windows Surface and Raspberry Pi are not supported and do not work correctly.

Once done read over the other documents in the repo on minimum requirements, HTTPS, security, etc. as well.