You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,6 @@ ARG WPR_WEB_PORT
29
29
ARG WPR_DOMAIN_NAME=localhost
30
30
ARG WPR_VIRTUAL_DIR=wscservice
31
31
ARG WPR_LICENSE_TICKET_ID
32
-
ARG WPR_PRODUCTS=4
33
-
ARG WPR_INSTALL_SAMPLES=1
34
32
```
35
33
* Choose languages to be installed:
36
34
```
@@ -69,7 +67,7 @@ ARG WPR_PROXY_PASSWORD=password
69
67
70
68
For details on the available options, refer to [Automated Installing WebSpellChecker on Linux](https://docs.webspellchecker.net/display/WebSpellCheckerServer55x/Automated+Installing+WebSpellChecker+on+Linux) guide.
71
69
72
-
4. If you need to use SSL (access the service via HTTPS), put your SSL certificate and key files to the `wproofreader-docker/files/certificate` directory. You need to rename your certificate files to `cert.pem` and `key.pem` accordingly.
70
+
4.SSL certificates (optional). If you need to use SSL (access the service via HTTPS) with your own certificates, put your SSL certificate and key files in the `wproofreader-docker/files/certificate` directory. By default, the expected filenames are `cert.pem` and `key.pem`, but you can customize them with the `WPR_CERT_FILE_NAME` and `WPR_CERT_KEY_NAME` build arguments. The files will be baked into the image at build time. Alternatively, you can mount certificates at runtime (see [Create and run Docker container](#create-and-run-docker-container)). If HTTPS is enabled and no certificates are provided, self-signed certificates will be generated automatically at container startup.
73
71
74
72
5. Build a Docker image using the command below:
75
73
@@ -146,8 +144,10 @@ where:
146
144
147
145
*`-d` start a container in detached mode.
148
146
*`-p 80:8080` map the host port `80:` and the exposed port of container `8080`, where port `8080` is a web server port (by default, NGINX). With the SSL connection, you must use port `443` like `-p 443:8443`.
149
-
*`-v <shared_dictionaries_directory>:/dictionaries` mount a shared directory where user and company custom dictionaries will be created and stored. Upon initial launch, the mounted directory may be empty. All essential subdirectories and files will be generated during initialization of the container. This is required to save the dictionaries among different containers. **Note!** The container user needs to have read and write permissions to the shared dictionary directory.
150
-
*`-v <certificate_directory_path>:/certificate` mount a shared directory where your SSL certificates are located. Use this option if you plan to work under SSL and you want to use a specific certificate for this container. The names of the files must be `cert.pem` and `key.pem`. If not specified, the default test SSL certificate (e.g. `ssl-cert-snakeoil`) shipped with Ubuntu will be used. **Note!** The container user must have read permissions for the certificate files.
147
+
*`-v <shared_dictionaries_directory>:/dictionaries` mount a shared directory where user and company custom dictionaries will be created and stored. Upon initial launch, the mounted directory may be empty. All essential subdirectories and files will be generated during initialization of the container. This is required to save the dictionaries among different containers.
148
+
Note: The container user needs to have read and write permissions to the shared dictionary directory.
149
+
*`-v <certificate_directory_path>:/certificate` mount a shared directory where your SSL certificates are located. Use this option if you plan to work under SSL and you want to use a specific certificate for this container. By default, the expected filenames are `cert.pem` and `key.pem` (configurable via `WPR_CERT_FILE_NAME` and `WPR_CERT_KEY_NAME`). If no certificates are provided (neither baked in at build time nor mounted at runtime), self-signed certificates will be generated automatically when the container starts with HTTPS enabled.
150
+
Note: The container user must have read permissions for the certificate files.
151
151
*`local/wsc_app:x.x.x` the tag of WebSpellChecker Server Docker image.
152
152
153
153
Alternatively, these parameters can be changed on the container running by passing them as environment variables:
@@ -292,7 +292,7 @@ Notes:
292
292
- WPR_DOMAIN_NAME=localhost
293
293
- WPR_VIRTUAL_DIR=wscservice
294
294
```
295
-
3. For HTTPS communication you have to provide your certificate file and key, as a pair of files named `cert.pem` and `key.pem`, respectively. If, for instance, they are kept in a folder `/home/user/certificate`, one should add the following section to `docker-compose.yml`:
295
+
3. For HTTPS communication you can provide your certificate file and key, as a pair of files named `cert.pem` and `key.pem` by default (configurable via `WPR_CERT_FILE_NAME` and `WPR_CERT_KEY_NAME`). If no certificates are mounted, self-signed certificates will be generated automatically at startup. To use your own certificates — for instance, if they are kept in a folder `/home/user/certificate` — add the following section to `docker-compose.yml`:
0 commit comments