Compare commits
4 Commits
Author | SHA1 | Date |
---|---|---|
Julien Fastré | 3616e4da20 | |
Julien Fastré | e2405d1eba | |
Julien Fastré | 004ad1a8da | |
Julien Fastré | 1e0b7b4ee4 |
|
@ -2,7 +2,7 @@ FROM ubuntu:16.04
|
|||
|
||||
MAINTAINER Julien Fastré <julienfastre@cvfe.be>
|
||||
|
||||
ARG version=3.2.9
|
||||
ARG version=3.1.5
|
||||
|
||||
WORKDIR /tmp/build
|
||||
|
||||
|
@ -31,7 +31,6 @@ RUN echo "untar SOPE sources" \
|
|||
postgresql-server-dev-9.5 \
|
||||
libmemcached-dev \
|
||||
libcurl4-openssl-dev \
|
||||
tzdata \
|
||||
&& echo "compiling sope & sogo" \
|
||||
&& cd /tmp/SOPE \
|
||||
&& ./configure --with-gnustep --enable-debug --disable-strip \
|
||||
|
|
21
README.md
21
README.md
|
@ -61,9 +61,6 @@ services:
|
|||
volumes:
|
||||
# replace by your own file
|
||||
- /path/to/your/file/sogo.conf:/etc/sogo/sogo.conf
|
||||
environment:
|
||||
# set the timezone in environment (see https://serverfault.com/a/826222/194817)
|
||||
- "TZ=Europe/Brussels"
|
||||
db:
|
||||
image: postgres:9.5
|
||||
# for debug purpose only: reach the database from outside
|
||||
|
@ -76,7 +73,6 @@ services:
|
|||
links:
|
||||
- sogo
|
||||
volumes_from:
|
||||
# you will be able to serve assets from sogo image
|
||||
- sogo:ro
|
||||
ports:
|
||||
# publish on port 80
|
||||
|
@ -88,7 +84,7 @@ services:
|
|||
|
||||
```
|
||||
|
||||
You should then be able to reach sogo on http://localhost:PORT/SOGo. Using the actual `nginx.conf` file **and** using a different port than the port 80 or 443, after login, you will encounter an http error on page `http://localhost/SOGo/<something>` Simply re-add the PORT number to reach correct server.
|
||||
You should then be able to reach sogo on http://localhost:8080/SOGo.
|
||||
|
||||
## How to build this image
|
||||
|
||||
|
@ -104,22 +100,9 @@ $ cd docker-sogo
|
|||
$ docker build --build-arg version=x.x.x .
|
||||
```
|
||||
|
||||
## Timezone issue
|
||||
|
||||
The timezone may be set in environement, using the `TZ` variable. See example in `docker-compose.yml`.
|
||||
|
||||
## migrating from 2.3 to 3.1|3.2 using docker-compose
|
||||
|
||||
The assets (css, js, ...) are contained in a volume. Those assets are completely different from version 2.3 to version 3.1 and 3.2. If you used `docker-compose` and migrated from 2.3 to 3.2, you have to either :
|
||||
The assets (css, js, ...) are contained in a volume. Those assets are completely different from version 2.3 to version 3.1 and 3.2. If you used `docker-compose` and migrated from 2.3 to 3.2, you have to remove the volume containing those assets, to let a clean place for the asset for the new version.
|
||||
|
||||
- remove the volume containing those assets, to let a clean place for the asset for the new version.
|
||||
- or use an anonymous volume, which will be re-created on each restart
|
||||
|
||||
## Usage of sendmail / `SOGoMailingMechanism`
|
||||
|
||||
Sendmail is not installed in this image: sogo must be able to send mails using a smtp server. The `sogo.conf` file must have the option `SOGoMailingMechanism` on `smtp`. See [the section "SMTP Server Configuration" of the sogo manual](https://sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf#33).
|
||||
|
||||
## Bug report
|
||||
|
||||
Please reports bug on https://github.com/julienfastre/docker-sogo/issues
|
||||
|
||||
|
|
|
@ -8,10 +8,10 @@ services:
|
|||
build:
|
||||
context: .
|
||||
args:
|
||||
- version=3.2.6a
|
||||
- version=3.1.5
|
||||
|
||||
# if you want to use builded image, uncomment next line
|
||||
# image: julienfastre/sogo:3.2
|
||||
# image: julienfastre/sogo:3.1
|
||||
|
||||
links:
|
||||
- db
|
||||
|
@ -20,8 +20,6 @@ services:
|
|||
# replace by the path to your own sogo.conf file
|
||||
|
||||
- ./../sogo.conf:/etc/sogo/sogo.conf
|
||||
environment:
|
||||
- "TZ=Europe/Amsterdam"
|
||||
db:
|
||||
image: postgres:9.5
|
||||
ports:
|
||||
|
|
Loading…
Reference in New Issue