Skip to content

Commit 27b9b2c

Browse files
authored
Update READMETEMPLATE.md
1 parent 2e9b486 commit 27b9b2c

File tree

1 file changed

+16
-33
lines changed

1 file changed

+16
-33
lines changed

READMETEMPLATE.md

Lines changed: 16 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
[forumurl]: https://forum.linuxserver.io
33
[ircurl]: https://www.linuxserver.io/irc/
44
[appurl]: www.example.com
5-
[dockerfileurl]: https://github.com/linuxserver/docker-<container-name>/blob/master/Dockerfile
6-
[hub]: https://hub.docker.com/r/<image-name>/
5+
[dockerfileurl]: https://github.com/linuxserver/docker-ldap-auth/blob/master/Dockerfile
6+
[hub]: https://hub.docker.com/r/ldap-auth/
77

88

99

@@ -29,25 +29,23 @@ The [LinuxServer.io][linuxserverurl] team brings you another image release featu
2929
+ weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
3030
+ security updates
3131

32-
# <image-name>
32+
# linuxserver/ldap-auth
3333

3434
[![Dockerfile-link](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/Dockerfile-Link-green.png)][dockerfileurl]
3535

36-
Provide a short, concise description of the application. No more than two SHORT paragraphs. Link to sources where possible and include an image illustrating your point if necessary. Point users to the original applications website, as that's the best place to get support - not here.
36+
The ldap-auth software is for authenticating users who request protected resources from servers proxied by nginx. It includes a daemon (ldap-auth) that communicates with an authentication server, and a webserver daemon that generates an authentication cookie based on the user’s credentials. The daemons are written in Python for use with a Lightweight Directory Access Protocol (LDAP) authentication server (OpenLDAP or Microsoft Windows Active Directory 2003 and 2012).
3737

38-
`IMPORTANT, replace all instances of <image-name> with the correct dockerhub repo (ie linuxserver/plex) and <container-name> information (ie, plex) and make sure to update the block at the top of this file containing app specific urls, dockerhub url and dockerfile url etc.`
3938

4039
&nbsp;
4140

4241
## Usage
4342

4443
```
4544
docker create \
46-
--name=<container-name> \
47-
-v <path to data>:/config \
48-
-e PGID=<gid> -e PUID=<uid> \
49-
-p 1234:1234 \
50-
<image-name>
45+
--name=ldap-auth \
46+
-p 8888:8888 \
47+
-p 9000:9000 \
48+
linuxserver/ldap-auth
5149
```
5250

5351
&nbsp;
@@ -59,35 +57,20 @@ For example with a port -p external:internal - what this shows is the port mappi
5957
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
6058
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.
6159

60+
NOTE: This container does not save any data that should be persistent and therefore there is no mapping for a `/config` folder.
6261

6362

6463
| Parameter | Function |
6564
| :---: | --- |
66-
| `-p 1234` | the port(s) |
67-
| `-v /config` | explain what lives here |
68-
| `-e PGID` | for GroupID, see below for explanation |
69-
| `-e PUID` | for UserID, see below for explanation |
65+
| `-p 8888` | the port for ldap auth daemon |
66+
| `-p 9000` | the port for ldap login page |
7067

71-
&nbsp;
72-
73-
## User / Group Identifiers
74-
75-
Sometimes when using volumes (`-v` flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
76-
77-
Ensure any volume directories on the host are owned by the same user you specify and it will "just work" &trade;.
78-
79-
In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below:
80-
81-
```
82-
$ id <dockeruser>
83-
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
84-
```
8568

8669
&nbsp;
8770

8871
## Setting up the application
8972

90-
Insert a basic user guide here to get a n00b up and running with the software inside the container. DELETE ME
73+
This container itself does not have any settings and it relies on the pertinent information passed in the form of http headers in incoming requests. Make sure that your webserver is set up with the right config. Here's a sample config: https://github.com/nginxinc/nginx-ldap-auth/blob/master/nginx-ldap-auth.conf
9174

9275

9376
&nbsp;
@@ -96,10 +79,10 @@ Insert a basic user guide here to get a n00b up and running with the software in
9679

9780
| Function | Command |
9881
| :--- | :--- |
99-
| Shell access (live container) | `docker exec -it <container-name> /bin/bash` |
100-
| Realtime container logs | `docker logs -f <container-name>` |
101-
| Container version | `docker inspect -f '{{ index .Config.Labels "build_version" }}' <container-name>` |
102-
| Image version | `docker inspect -f '{{ index .Config.Labels "build_version" }}' <image-name>` |
82+
| Shell access (live container) | `docker exec -it ldap-auth /bin/bash` |
83+
| Realtime container logs | `docker logs -f ldap-auth` |
84+
| Container version | `docker inspect -f '{{ index .Config.Labels "build_version" }}' ldap-auth` |
85+
| Image version | `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/ldap-auth` |
10386
| Dockerfile | [Dockerfile][dockerfileurl] |
10487

10588
&nbsp;

0 commit comments

Comments
 (0)