deac/docker-sogo
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Adding build info + grammar, removing docker tags (not pushed on docker hub)

Browse source
This commit is contained in:
Julien Fastré 2016-08-09 12:54:05 +02:00
parent c63950b200
commit 48723af681
1 changed files with 20 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
README.md
View file

@ -1,8 +1,3 @@
# Supported tags and respective `Dockerfile` links
- `3.1.4`, `3.1`, `latest`
# What is SOGo ? # What is SOGo ?
SOGo (formerly named Scalable OpenGroupware.org) is an open source collaborative software (groupware) server with a focus on simplicity and scalability. It is developed in Objective-C using PostgreSQL, Apache, and IMAP. SOGo (formerly named Scalable OpenGroupware.org) is an open source collaborative software (groupware) server with a focus on simplicity and scalability. It is developed in Objective-C using PostgreSQL, Apache, and IMAP.
@ -23,17 +18,22 @@ Since July 2016, Inverse Inc. [ask for some support](https://sogo.nu/nc/support/
# How to use this image # How to use this image
The requires : This image requires :
- a working IMAP and SMTP server (not provided under docker container) ; - a working IMAP and SMTP server (not provided under docker container) ;
- a postgresql / mysql database ; - a postgresql / mysql database ;
- memcached ; - memcached ;
- some way to authenticate user: LDAP, SQL table, ... (see [the docs](SOGoInstallationGuide.pdf)) - some way to authenticate user: LDAP, SQL table, ... (see [the docs](SOGoInstallationGuide.pdf))
- a configuration file
Using the pattern one container = one process, this container only execute the `sogod` process. This container only execute the `sogod` process, [taking into account the best practice "running one process per container"](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/run-only-one-process-per-container).
In order to run it You should create an adapt a config file to your needs, [using the docs](SOGoInstallationGuide.pdf). This file should be recorded into the container as `/etc/sogo/sogo.conf`. In order to run it You should create an adapt a config file to your needs, [using the docs](SOGoInstallationGuide.pdf). This file should be recorded into the container as `/etc/sogo/sogo.conf`.
## Using the command line
**TO BE DONE**
## Using docker-compose ## Using docker-compose
This is a `docker-compose.yml` file you could adapt to launch this image : This is a `docker-compose.yml` file you could adapt to launch this image :
@ -82,3 +82,16 @@ You should then be able to reach sogo on http://localhost:8080/SOGo.
**Warning** after login, the redirection does not work and you will reach http://localhost/SOGo/<your path> instead of http://localhost:8080/SOGo/<your path>. Simply add the missing port part. **Warning** after login, the redirection does not work and you will reach http://localhost/SOGo/<your path> instead of http://localhost:8080/SOGo/<your path>. Simply add the missing port part.
## How to build this image
The parameter `version` is required to build this image.
Example of how to build this image :
```
# download sources
$ git clone https://framagit.org/julienfastre/docker-sogo.git
$ cd docker-sogo
# launch the build using the version 3.1.4
$ docker build --build-arg version=3.1.4 .
```