... | ... | @@ -33,9 +33,9 @@ The Windows installer packages for the various environments can be downloaded fr |
|
|
|
|
|
PEP client software for Linux is distributed as Docker containers. While these containers (obviously) provide PEP binaries such as `pepcli`, previous versions did not include the configuration needed to connect to (specific) project environments. Users were instead required to provide such configuration themselves, e.g. starting containers with a `--volume` (or the `-v` equivalent) switch to expose the configuration files to the container.
|
|
|
|
|
|
The new deployment mechanism introduces `client` Docker images that include configuration files to connect to a specific PEP environment. Users should switch to using the new client images instead of other PEP images they may be using. To run Docker containers based on the new images, please perform the following steps. Note that things should keep working after each individual step.
|
|
|
The new deployment mechanism introduces `client` Docker images that include configuration files to connect to a specific PEP environment. Users should switch to using the new client images instead of other PEP images they may be using. To run Docker containers based on the new images, please perform the following steps. Note that `pepcli` invocations should keep working after each individual step.
|
|
|
|
|
|
1. Change your `docker run` and/or `docker exec` command lines to use the new image registry location instead of the one you've been using. The table below lists the tags to feed into your commands.
|
|
|
1. Change your `docker run` and/or `docker exec` command lines to use the new image registry location instead of the one you've been using. The table below lists the image tags to use for the various PEP environments.
|
|
|
2. Update your `pepcli` command lines so that the executable uses the configuration in the `/config` directory included in the image, e.g. specify the `--client-working-directory /config` switch, or `cd /config` before invoking `pepcli`.
|
|
|
3. Stop providing external configuration files (using `--volume` or `-v` switches) to the Docker container. Note that users must (still) provide
|
|
|
- any user specific data: e.g. if you used to pass an `--oauth-token` to `pepcli`, you'll still need to provide it. And if you point the `--oauth-token` switch to a (JSON) file, you'll still need to run Docker with a `--volume` switch to make the file available to the container.
|
... | ... | |