Installation

This page describes proven deployment scenarios for eccenca Corporate Memory.

All Corporate Memory components are distributed as Docker images and can be obtained from eccenca’s container repository service. To run them you need a Docker enabled Linux server.

Operating Systems (OS)

Corporate Memory is tested on Ubuntu 24.04 (backward compatible with LTS versions older than that) as Debian 11, 12 and 13.

Special note on RHEL SELinux Support: there is no limitation for RedHat SELinux. We recommend to keep the SELinux in enforced mode. You can keep the default setting of the /etc/selinux/config file.

sample config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=enforcing
# SELINUXTYPE= can take one of three values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected.
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

Docker compose based Orchestration deployment

Docker Compose is a convenient way to provision several Docker containers locally for development setups or on remote servers for single node setups.

eccenca is heavily using docker compose for all kinds of internal and customer deployments. For more details on how to use docker compose based orchestration refer to Scenario: Local Installation and Scenario: Single Node Cloud Installation.

Helm based Kubernetes deployment

Most production deployments are Kubernetes based. We have deployments in AWS (EKS), Azure (AKS), Red Hat Openshift and self-hosted clusters. We provide Charts for Corporate Memory and Keycloak at our Helm Repository. For more details on how to use helm based deployments refer to Scenario: Kubernetes Deployment.

Comments