5835fa09d7
Answers "should we stop creating an admin/pass on start" with the split the catalog actually has, rather than one way for everything. Ten apps need it: adguard, authelia, bookstack, matrix, nextcloud, owncloud, pihole, rocketchat, stalwart, speedtest and headscale either pass the generated password into the container or hand it to an install hook that creates the account. There the password IS the working credential — dropping it would lock you out. Left alone. Three do not create an account at all: gitea, invidious and mattermost seed no user (the first one comes from their own signup flow or the Create Account tool), so the password minted at install named nothing. The WebUI credentials card showed a password that could not log in. They now match linkding — an empty, unslotted ADMIN_PASSWORD the auth adapter fills when the operator makes the first admin, and keeps in step on later resets. Unslotted because the slot number marks a value the installer generates. mattermost's adapter also had linkding's bug: it persists ADMIN_PASSWORD but the config declared only ADMIN_EMAIL, so the write was a no-op. WebUI: rocketchat's generated admin password had no field mapping, so the card could not show it. Added, plus a generic ADMIN_USER entry — six apps record an admin username the card had no way to display. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
11 lines
278 B
Bash
11 lines
278 B
Bash
#!/bin/bash
|
|
|
|
appRocketchatCreateAccount() {
|
|
local args="$1"
|
|
authAdapterCall rocketchat createUser \
|
|
"$(authToolArg "$args" email)" \
|
|
"$(authToolArg "$args" password)" \
|
|
"$(authToolArg "$args" username)" \
|
|
"$(authToolArg "$args" admin)"
|
|
}
|