Compare commits

...

6 commits

Author SHA1 Message Date
Simon L.
481604507c
Merge pull request #6906 from nextcloud/dev/6892/fix
Some checks failed
Codespell / Check spelling (push) Waiting to run
Validate community containers / Validate community containers (push) Has been cancelled
Json Validator / Json Validator (push) Has been cancelled
Change ui_secret to use LLDAP_LDAP_USER_PASS
2025-10-06 16:07:08 +02:00
Simon L.
7fbc548d2d lldap: adjust hint how to retrieve the password
Signed-off-by: Simon L. <szaimen@e.mail.de>
2025-10-06 15:44:27 +02:00
Simon L.
3ad84e2ae0
Merge pull request #6916 from nextcloud/alexanderdd-patch-1
add comment about possibility of migration AIO->VM
2025-10-06 15:23:57 +02:00
Simon L.
a33ef5d1aa move the hint to a new line
Signed-off-by: Simon L. <szaimen@e.mail.de>
2025-10-06 15:12:31 +02:00
Alexander Müller
b77af1a2f8
add comment about possibility of migration AIO->VM
Signed-off-by: Alexander Müller <28591861+alexanderdd@users.noreply.github.com>
2025-09-28 14:10:59 -05:00
Jean-Yves
f8cc109b7e
Change ui_secret to use LLDAP_LDAP_USER_PASS
Signed-off-by: Jean-Yves <7360784+docjyJ@users.noreply.github.com>
2025-09-27 12:26:56 +02:00
3 changed files with 4 additions and 6 deletions

View file

@ -27,7 +27,7 @@
"LLDAP_JWT_SECRET",
"LLDAP_LDAP_USER_PASS"
],
"ui_secret": "LLDAP_JWT_SECRET",
"ui_secret": "LLDAP_LDAP_USER_PASS",
"volumes": [
{
"source": "nextcloud_aio_lldap",

View file

@ -18,10 +18,7 @@ Functionality with this configuration:
> For simplicity, this configuration is done via the command line (don't worry, it's very simple).
First, you need to retrieve the LLDAP admin password, this will be used later on. Which you need to type in or copy and paste:
```bash
sudo docker inspect nextcloud-aio-lldap | grep LLDAP_LDAP_USER_PASS
```
First, you need to retrieve the LLDAP admin password that you can see next to the container in the AIO interface. There you can configure smtp first and then invite users via mail.
Now go into the Nextcloud container:<br>
**Please note:** If you do not have CLI access to the server, you can now run docker commands via a web session by using this community container: https://github.com/nextcloud/all-in-one/tree/main/community-containers/container-management. This script below can be run from inside the container-management container via `bash /lldap.sh`.

View file

@ -52,7 +52,8 @@ Included are:
- Possibility included to [pass the needed device for hardware transcoding](https://github.com/nextcloud/all-in-one#how-to-enable-hardware-acceleration-for-nextcloud) to the Nextcloud container
- Possibility included to [store all docker related files on a separate drive](https://github.com/nextcloud/all-in-one#how-to-store-the-filesinstallation-on-a-separate-drive)
- [LDAP can be used as user backend for Nextcloud](https://github.com/nextcloud/all-in-one/tree/main#ldap)
- Migration from any former Nextcloud installation to AIO is possible. See [this documentation](https://github.com/nextcloud/all-in-one/blob/main/migration.md)
- Migration from any former Nextcloud installation to AIO is possible. See [this documentation](https://github.com/nextcloud/all-in-one/blob/main/migration.md).
- Migration in the other direction (e.g. from AIO to a VM-based installation) is also possible.
- [Fail2Ban can be added](https://github.com/nextcloud/all-in-one#fail2ban)
- [phpMyAdmin, Adminer or pgAdmin can be added](https://github.com/nextcloud/all-in-one#phpmyadmin-adminer-or-pgadmin)
- [Mail server can be added](https://github.com/nextcloud/all-in-one#mail-server)