Scenario: Single Node Cloud Installation¤
This page describes a docker-compose based orchestration running on a server instance accessible publicly via browser (SSL enabled via letsencrypt).
- ssh access to a server instance (Debian 10) with a public IP address
- A resolvable domain name to this server
- Terminal with ssh client installed locally
- An eccenca partner account for the docker registry as well as the release artifact area
In this step, you install necessary software on the server and execute the following commands as root:
For username and password in curl command use the credentials to access eccenca Artifactory and docker registry.
Connect to the server and navigate to the directory with the Corporate Memory docker orchestration:
The Corporate Memory docker orchestration is configured with environment files.
You will need to create an environment file at
/opt/cmem-orchestration/environments/prod.env - for now, you can use the provide file
config.ssl-letsencrypt.env as a template.
You need to change the lines with DEPLOYHOST and LETSENCRYPT_MAIL to you actual values.
In addition that, you need to remove the default config and link it to your prod.env
To see all available configuration options refer to Docker Orchestration configuration page.
Next, request SSL certificates from letsencrypt service:
Change CMEM_BASE_URI according to your DEPLOYHOST.
Finally deploy the Corporate Memory instance:
Optional: you can install cmem as a systemd service for this use these commands as root oder sudo:
Validation and Finalisation¤
Open your browser and navigate to the host you have created in DNS server, e.g. [https://corporate-memory.eccenca.dev]https://corporate-memory.eccenca.dev/
Click CONTINUE WITH LOGIN and use one of these default accounts:
||Is member of the global admin group (can see and do anything)|
||Is member of the local user group (can not change access conditions or see internal graphs)|
After successful login, you will see Corporate Memory interface. You can now proceed to the Getting Started section.
Do not forget to change the passwords of your deployment, especially if it is available from the public internet. For this, take a look at Change Passwords and Keys.
Change the passwords for your needs
- To login in to keycloak and change the passwords
- To change keycloak admin
- To change cmem admin
- To change cmem user
- To change OAUTH_CLIENT_SECRET