docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

In Silverpeas, inform about the choice of Data Volume Container over the simple shared-storage volumes

This commit is contained in:
Miguel Moquillon 2016-12-09 10:59:27 +01:00
parent 4f28f6b154
commit 1286f952f1
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
silverpeas/content.md
View File

@ -100,17 +100,21 @@ For a PostgreSQL database system, some configurations are required in order to b
# Using a Data Volume Container # Using a Data Volume Container
To manage more effectively the data produced by an application, the Docker team recommends to use a Data Volume Container. In Silverpeas, there are four types of data produced by the application: The data produced by Silverpeas mean to be persistent, available for the next versions of Silverpeas, and they have to be accessible to other containers like the one running LibreOffice. For doing, the Docker team recommends to use a Data Volume Container.
In Silverpeas, there are four types of data produced by the application:
- the logging stored in `/opt/silverpeas/log`, - the logging stored in `/opt/silverpeas/log`,
- the user data and those produced by Silverpeas from the user data in `/opt/silverpeas/data`, - the user data and those produced by Silverpeas from the user data in `/opt/silverpeas/data`,
- the user domains and the domain authentication definitions in respectively `/opt/silverpeas/properties/org/silverpeas/domains` and `/opt/silverpeas/properties/org/silverpeas/authentication`, - the user domains and the domain authentication definitions created in the backoffice in respectively `/opt/silverpeas/properties/org/silverpeas/domains` and `/opt/silverpeas/properties/org/silverpeas/authentication`,
- the workflows created by the workflow editor in `/opt/silverpeas/xmlcomponents/workflows`. - the workflows created by the workflow editor in `/opt/silverpeas/xmlcomponents/workflows`.
Beside these directories, according to your specific needs, custom configuration scripts can be added in the directories `/opt/silverpeas/configuration/jboss` and `/opt/silverpeas/configuration/silverpeas`. Beside these directories, according to your specific needs, custom configuration scripts can be added in the directories `/opt/silverpeas/configuration/jboss` and `/opt/silverpeas/configuration/silverpeas`.
The directories `/opt/silverpeas/log`, `/opt/silverpeas/data`, `/opt/silverpeas/properties`, `/opt/silverpeas/xmlcomponents/workflows`, and `/opt/silverpeas/configuration` are all defined as volumes in the Docker image. The directories `/opt/silverpeas/log`, `/opt/silverpeas/data`, `/opt/silverpeas/properties`, `/opt/silverpeas/xmlcomponents/workflows`, and `/opt/silverpeas/configuration` are all defined as volumes in the Docker image.
All these different kind of data have to be consistent for a given state of Silverpeas; they form a coherent whole. Then, defining a Data Volume Container to gather all of these volumes is a better solution over multiple shared-storage volume definitions. You can, with a such Data Volume Container, backup, restore or migrate more easily the full set of the data of Silverpeas.
To define a Data Volume Container for Silverpeas, for example: To define a Data Volume Container for Silverpeas, for example:
$ docker create --name silverpeas-store \ $ docker create --name silverpeas-store \