0
0
Fork 0
mirror of https://github.com/nextcloud/docker.git synced 2024-11-05 22:04:58 +01:00
nextcloud-docker/.examples/README.md

50 lines
2.7 KiB
Markdown
Raw Normal View History

2017-08-16 18:01:14 +02:00
# Examples section
In this subfolders are some examples how to use the docker image. There are two sections:
* [`dockerfiles`](https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles)
2017-08-16 18:05:22 +02:00
* [`docker-compose`](https://github.com/nextcloud/docker/tree/master/.examples/docker-compose)
2017-08-16 18:01:14 +02:00
The `dockerfiles` are derived images, that add or alter certain functionalities of the default docker images. In the `docker-compose` subfolder are examples for deployment of the application, including database, redis, collabora and other services.
## Dockerfiles
2017-08-16 18:05:22 +02:00
The Dockerfiles use the default images as base image and build on top of it.
2017-08-16 18:01:14 +02:00
Example | Description
------- | -------
2017-08-16 18:34:01 +02:00
[cron](https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles/cron) | uses supervisor to run the cron job inside the container (so no extra container is needed).
[imap](https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles/imap) | adds dependencies required to authenticate users via imap
[smb](https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles/smb) | adds dependencies required to use smb shares
2017-08-16 18:01:14 +02:00
## docker-compose
2017-08-16 18:05:22 +02:00
In `docker-compose` additional services are bundled to create a complete nextcloud installation. The examples are designed to run out-of-the-box.
2017-08-16 18:25:16 +02:00
Before running the examples you have to modify the `db.env` and `docker-compose` file and fill in your custom information.
2017-08-16 18:01:14 +02:00
**TODO: ADD INSECURE DESCRIPTION**
### with-nginx-proxy
The nginx proxy adds a proxy layer between nextcloud and the internet. The proxy is designed to serve multiple sites on the same host machine.
2017-08-16 18:05:22 +02:00
The advantage in adding this layer is the ability to add a container for [Let's Encrypt](https://letsencrypt.org/) certificate handling.
This combination of the [jwilder/nginx-proxy](https://github.com/jwilder/nginx-proxy) and [jrcs/docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion) containers creates a fully automated https encryption of the nextcloud installation without worrying about certificate generation, validation or renewal.
2017-08-16 18:01:14 +02:00
To use this example complete the following steps:
1. open docker-compose.yml
2017-08-16 18:07:16 +02:00
1. insert your nextcloud domain behind `VIRTUAL_HOST=`and `LETSENCRYPT_HOST=`
2. enter a valid email behind `LETSENCRYPT_EMAIL`
3. choose a root password for the database behin `MYSQL_ROOT_PASSWORD=`
4. enter your collabora domain behind `domain=`
2017-08-16 18:01:14 +02:00
2. choose a password for the database user nextcloud in `db.env`behind `MYSQL_PASSWORD`
3. run `docker-compose build --pull` to pull the most recent base images and build the custom dockerfiles
4. start nextcloud with `docker-compose up -d`
If you want to update your installation to a newer version of nextcloud, repeat the steps 3 and 4.