| |
@@ -48,11 +48,11 @@
|
| |
|
| |
The easiest way to setup a 389 server to test with this is in a docker container:
|
| |
|
| |
- docker run -v 389data:/data -i -t 389ds/dirsrv:latest
|
| |
+ docker run --name=389-ds -v 389data:/data -i -t 389ds/dirsrv:latest
|
| |
|
| |
You can then run this project in a container such as:
|
| |
|
| |
- docker run -v 389data:/data -i -t opensuse/tumbleweed:latest /bin/sh
|
| |
+ docker run --name=389-ds-portal -v 389data:/data -p 8080 -i -t opensuse/tumbleweed:latest /bin/sh
|
| |
|
| |
To run this you will require python3, python3-Flask and temporarily python3-cryptography.
|
| |
|
| |
@@ -68,3 +68,24 @@
|
| |
|
| |
py.test ./test.py
|
| |
|
| |
+ Docker
|
| |
+ ------
|
| |
+
|
| |
+ To build the image run:
|
| |
+
|
| |
+ docker build -t 389-ds-portal:devel .
|
| |
+
|
| |
+ Then to run it with an instance:
|
| |
+
|
| |
+ docker run --name=389-ds -v 389data:/data -i -t 389ds/dirsrv:latest
|
| |
+ docker run --name=389-ds-portal -v 389data:/data -p 8080:8080 -i -t 389-ds-portal:devel
|
| |
+
|
| |
+ You may need to add some users to the container such as:
|
| |
+
|
| |
+ docker exec -i -t 389-ds /usr/sbin/dsconf localhost backend create --be-name userRoot --suffix dc=example,dc=com
|
| |
+ docker exec -i -t 389-ds /usr/sbin/dsidm -b dc=example,dc=com localhost initialise
|
| |
+ docker exec -i -t 389-ds /usr/sbin/dsidm -b dc=example,dc=com localhost user create --uid william --cn william --displayName william --uidNumber 1000 --gidNumber 1000 --homeDirectory /home/william
|
| |
+ docker exec -i -t 389-ds /usr/sbin/dsidm -b dc=example,dc=com localhost account reset_password uid=william,ou=People,dc=example,dc=com
|
| |
+
|
| |
+ Now you should be able to use the portal as a test.
|
| |
+
|
| |
This adds a dockerfile and support for docker to the 389-ds-portal. This may not work for others yet due to: