@@ -13,27 +13,26 @@ To create an image, just do:
13
13
14
14
$ ./build.sh
15
15
16
- this will build an image to work on the latest version of Silverpeas as defined in the ` Dockerfile `
17
- with the tag ` silverpeas/silverdev:latest ` .
16
+ this will build an image to work on the latest version of Silverpeas and with the latest supported
17
+ version of Wildfly as defined in the ` Dockerfile ` with the tag ` silverpeas/silverdev:latest ` .
18
18
19
- Otherwise, to create an image to build a given version of Silverpeas 6, you have to specify as argument
20
- both the version of Silverpeas followed by the exact version of Wildfly used by this version :
19
+ To specify both a given version of Wildfly (for instance Wildfly 10.1.0) to use and the version of
20
+ the image to set, just do :
21
21
22
- $ ./build.sh -v 6.0 10.1.0
22
+ $ ./build.sh -w 10.1.0 -v 6 .0
23
23
24
- This will build a Docker image with the tag ` silverpeas/silverdev:6.0 ` . It is to work on a
25
- Silverpeas 6.0 project and with Wildfly 10.1.0. Here, the version of Silverpeas passed as argument
26
- isn't in fact important; it just a convention stipulating that a tag of an image is the version
27
- of the Silverpeas projects for which it was created. By doing so, it will be easy for the developer
28
- to switch between different containers, each of them prepared for a different version of Silverpeas.
29
- But the version of Wildfly passed as argument is important because a Wildfly distribution preconfigured
30
- for the integration tests will be downloaded and in general, for each version of Silverpeas
24
+ This will build a Docker image with the tag ` silverpeas/silverdev:6.0 ` . By convention, the version of
25
+ the Docker image should be the same of the version of Silverpeas for which the image is dedicated. It
26
+ is mainly for information so what, by doing so, it will be easy for the developer to switch between
27
+ different containers, each of them prepared for a different version of Silverpeas.
28
+ Nevertheless, the version of Wildfly passed as argument is important because a Wildfly distribution
29
+ preconfigured for the integration tests will be downloaded and in general, for each version of Silverpeas
31
30
(stable or in-development version) matches a given version of Wildfly.
32
31
33
32
The image is created to start a container with a default user (` silveruser ` ). 1000 is his identifier
34
33
and ` users ` (group identifier 100) is its main group.
35
34
In order to avoid permissions problems with the source code that is shared between the host and the
36
- container, it is required that the identifier of your account in your host is the same that the
35
+ container(s) , it is required that the identifier of your account in your host is the same that the
37
36
identifier of the default user in the container. In the case your user identifier isn't 1000, then you have to
38
37
create an image by specifying the identifier in the command line as following (here, in our example,
39
38
the user identifier is 1026):
0 commit comments