This is a multi-instance setup of ownCloud where both instances sit behind a reverse proxy. The intent of the project is to make is easier to test functionality of ownCloud that requires interaction between multiple instances, as well as a, potential, template for building multi-instance setups (that's a latter thought that is perhaps a coincidental benefit, rather than a stated aim).
When initially checked out, the project will not build if you run docker-compose up, as the following files are missing:
- The ownCloud source for both ownCloud instances
- The SSL certificates
You need to clone two copies of the ownCloud source, which need to be placed in owncloud/community/owncloud-server-1 and owncloud/community/owncloud-server-2, respectively.
You need to:
- Generate private keys for both servers
- Generate a root certificate
- Sign each server’s private keys using the root certificate
If you’re not familiar with doing all this, here are two tutorials that step you through how to do it:
- How to Create Your Own SSL Certificate Authority for Local HTTPS Development
- How to Be Your Own Certificate Authority
After you’ve completed the setup, you then need to install the files in the relevant directories under docker/files/etc/ssl.
You can see the locations and names in docker-compose.yml.
Once SSL certificates have been created, signed, and stored, then you can start the containers by running the following command:
docker-compose up -d --build
This should start them all in a few minutes.
You can check on progress using one of two commands: ps and logs.
There are examples of how to use both in the example below.
docker-compose ps
docker-compose logs --follow
