COmanage Registry Docker
This repository contains Dockerfiles, documenation, and other files necessary to build and deploy a Dockerized version of COmanage Registry, as well as other infrastructure commonly deployed with COmanage Registry.
Since COmanage Registry is a web application that requires a relational database and an authentication mechanism such as Shibboleth, mod_auth_openidc, or just simple Basic Authentication, this repository includes multiple Dockerfiles to build images that use various combinations of tools.
Evaluate COmanage Registry
If you are new to COmanage Registry follow these instructions to build and run a simple deployment suitable for evaluating COmanage Registry.
Building Images
The following link to detailed instructions for building each individual image. See the next section for links to documentation on how to deploy the images as services.
- COmanage Registry base image
- COmanage Registry with Basic Authentication
- COmanage Registry for Developers with Basic Authentication
- COmanage Registry with Shibboleth SP base image
- COmanage Registry with Shibboleth SP
- COmanage Registry with mod_auth_openidc
- COmanage Registry for InCommon TAP base
- COmanage Registry for InCommon TAP
- COmanage Registry cron for executing JobShell jobs
- PostgreSQL for COmanage Registry
- OpenLDAP slapd base for COmanage Registry
- OpenLDAP slapd for COmanage Registry
- OpenLDAP slapd proxy for COmanage Registry
Deploying Images and Running Services
Since COmanage Registry requires a relational database, and because it is often deployed with other tools like an LDAP directory, multiple images need to be simultanesouly instantiated as containers. Orchestrating multiple containers to create services is easiest using tools such as Docker Compose, Docker Swarm, or Kubernetes.
The images built from Dockerfiles in this repository may be used with any container orchestration platform but the documentation demonstrates how to deploy with Docker Swarm (the simple evaluation scenario above uses Docker Compose).
The following link to detailed instructions for a number of deployment scenarios.
- COmanage Registry using the Shibboleth SP and PostgreSQL database
- COmanage Registry using the Shibboleth SP and MariaDB database
- COmanage Registry using mod_auth_openidc and MariaDB database
- COmanage Registry using the InCommon TAP image
- Adding an OpenLDAP Directory
- Adding an OpenLDAP proxy server
All Documentation
Building Images
- COmanage Registry base image
- COmanage Registry with Basic Authentication
- COmanage Registry for Developers with Basic Authentication
- COmanage Registry with Shibboleth SP base image
- COmanage Registry with Shibboleth SP
- COmanage Registry with mod_auth_openidc
- COmanage Registry for InCommon TAP base
- COmanage Registry for InCommon TAP
- PostgreSQL for COmanage Registry
- OpenLDAP slapd base for COmanage Registry
- OpenLDAP slapd for COmanage Registry
- OpenLDAP slapd proxy for COmanage Registry
Deploying Services
- COmanage Registry using the Shibboleth SP and PostgreSQL database
- COmanage Registry using the Shibboleth SP and MariaDB database
- COmanage Registry using mod_auth_openidc and MariaDB database
- COmanage Registry using the InCommon TAP image
- Adding an OpenLDAP Directory
- Adding an OpenLDAP proxy server
Other
- COmanage Registry Volumes and Data Persistence
- Evaluating COmanage Registry using Docker
- Environment Variables Common to All Images
- Environment Variables Common to Images using Shibboleth SP for Authentication
- Environment Variables Common to All slapd Images
- Executing LDIF Files
- OpenLDAP slapd for COmanage Registry Volumes and Data Persistence
- Simple Development Sandbox
- Simple Plugin Development Sandbox with MariaDB
