adding a volume with webresources

those webresources are share with a nginx container, and contains css / js
This commit is contained in:
Julien Fastré 2016-10-28 14:14:09 +02:00
parent 72072d87b3
commit 47d7203928
3 changed files with 29 additions and 15 deletions

View file

@ -53,6 +53,8 @@ RUN echo "untar SOPE sources" \
# add sogo.conf # add sogo.conf
ADD sogo.default.conf /etc/sogo/sogo.conf ADD sogo.default.conf /etc/sogo/sogo.conf
VOLUME /usr/local/lib/GNUstep/SOGo/WebServerResources
EXPOSE 20000 EXPOSE 20000
USER sogo USER sogo

View file

@ -12,7 +12,7 @@ Microsoft Outlook support is provided through an OpenChange storage provider to
# Use with care and contribute to Inverse Inc # Use with care and contribute to Inverse Inc
This image is still experimental. Use with care. This image is in use in a organization of 80 people, without any known problem (except when we migrated from 2.3 to 3.2, see above).
Since July 2016, Inverse Inc. [ask for some support](https://sogo.nu/nc/support/faq/article/why-production-packages-required-a-support-contract-from-inverse.html) to provide debian packages. This should help them to increase their investments in SOGo. If you can afford [this](https://sogo.nu/support/index_new.html#/commercial), you should consider getting support on Inverse Inc. Since July 2016, Inverse Inc. [ask for some support](https://sogo.nu/nc/support/faq/article/why-production-packages-required-a-support-contract-from-inverse.html) to provide debian packages. This should help them to increase their investments in SOGo. If you can afford [this](https://sogo.nu/support/index_new.html#/commercial), you should consider getting support on Inverse Inc.
@ -48,15 +48,14 @@ services:
build: build:
context: . context: .
args: args:
version: 3.1.5 # replace by your desired version
# if you prefer using a pre-built image version: x.x.x
# image: julienfastre/sogo:3.1 # if you prefer using a pre-built image (replace by your desired version)
# image: julienfastre/sogo:x.x
links: links:
- db - db
volumes: volumes:
# required to allow nginx to access to resources # replace by your own file
- /usr/local/lib/GNUstep/SOGo/WebServerResources/
# create
- /path/to/your/file/sogo.conf:/etc/sogo/sogo.conf - /path/to/your/file/sogo.conf:/etc/sogo/sogo.conf
db: db:
image: postgres:9.5 image: postgres:9.5
@ -95,3 +94,10 @@ $ cd docker-sogo
# launch the build using the version 3.1.5 # launch the build using the version 3.1.5
$ docker build --build-arg version=3.1.5 . $ docker build --build-arg version=3.1.5 .
``` ```
## 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 remove the volume containing those assets, to let a clean place for the asset for the new version.

View file

@ -2,18 +2,24 @@ version: '2'
services: services:
sogo: sogo:
# if you want to build your own image # if you want to build your own image
# build:
# context: . build:
# args: context: .
# - version=2.3.16 args:
# if you want to use builded image - version=3.2.0
image: julienfastre/sogo:3.1
# if you want to use builded image, uncomment next line
# image: julienfastre/sogo:3.1
links: links:
- db - db
volumes: volumes:
- /usr/local/lib/GNUstep/SOGo/WebServerResources/
- /path/to/my/sogo.conf:/etc/sogo/sogo.conf # replace by the path to your own sogo.conf file
- ./../sogo.conf:/etc/sogo/sogo.conf
db: db:
image: postgres:9.5 image: postgres:9.5
ports: ports: