vaultwarden-alternativa-bit.../docker/start.sh

#!/bin/sh

if [ -n "${UMASK}" ]; then
    umask "${UMASK}"
fi

if [ -r /etc/vaultwarden.sh ]; then
    . /etc/vaultwarden.sh
elif [ -r /etc/bitwarden_rs.sh ]; then
    echo "### You are using the old /etc/bitwarden_rs.sh script, please migrate to /etc/vaultwarden.sh ###"
    . /etc/bitwarden_rs.sh
fi

if [ -d /etc/vaultwarden.d ]; then
    for f in /etc/vaultwarden.d/*.sh; do
        if [ -r "${f}" ]; then
            . "${f}"
        fi
    done
elif [ -d /etc/bitwarden_rs.d ]; then
    echo "### You are using the old /etc/bitwarden_rs.d script directory, please migrate to /etc/vaultwarden.d ###"
    for f in /etc/bitwarden_rs.d/*.sh; do
        if [ -r "${f}" ]; then
            . "${f}"
        fi
    done
fi

exec /vaultwarden "${@}"
Add startup script to support init operations This is useful for making local customizations upon container start. To use this feature, mount a script into the container as `/etc/bitwarden_rs.sh` and/or a directory of scripts as `/etc/bitwarden_rs.d`. In the latter case, only files with an `.sh` extension are sourced, so files with other extensions (e.g., data/config files) can reside in the same dir. Note that the init scripts are run each time the container starts (not just the first time), so these scripts should be idempotent. 2020-07-06 00:26:20 +02:00			`#!/bin/sh`

Allow custom umask setting (#4896) To provide a way to add more security regarding file/folder permissions this PR adds a way to allow setting a custom `UMASK` variable. This allows people to set a more secure default like only allowing the owner the the process/container to read/write files and folders. Examples: - `UMASK=022` File: 644 \| Folder: 755 (Default of the containers) This means Owner read/write and group/world read-only - `UMASK=027` File: 640 \| Folder: 750 This means Owner read/write, group read-only, world no access - `UMASK=077` File: 600 \| Folder: 700 This measn Owner read/write and group/world no access resolves #4571 Signed-off-by: BlackDex <black.dex@gmail.com> 2024-08-27 19:37:17 +02:00			`if [ -n "${UMASK}" ]; then`
			`umask "${UMASK}"`
			`fi`

Project renaming 2021-04-27 23:18:32 +02:00			`if [ -r /etc/vaultwarden.sh ]; then`
			`. /etc/vaultwarden.sh`
Remove warning when compiling only with mysql and add compatibility mode with the old docker script names 2021-04-29 15:58:29 +02:00			`elif [ -r /etc/bitwarden_rs.sh ]; then`
			`echo "### You are using the old /etc/bitwarden_rs.sh script, please migrate to /etc/vaultwarden.sh ###"`
			`. /etc/bitwarden_rs.sh`
Add startup script to support init operations This is useful for making local customizations upon container start. To use this feature, mount a script into the container as `/etc/bitwarden_rs.sh` and/or a directory of scripts as `/etc/bitwarden_rs.d`. In the latter case, only files with an `.sh` extension are sourced, so files with other extensions (e.g., data/config files) can reside in the same dir. Note that the init scripts are run each time the container starts (not just the first time), so these scripts should be idempotent. 2020-07-06 00:26:20 +02:00			`fi`

Project renaming 2021-04-27 23:18:32 +02:00			`if [ -d /etc/vaultwarden.d ]; then`
			`for f in /etc/vaultwarden.d/*.sh; do`
Update deps and Alpine image - Updated deps - Updated Alpine images to 3.16 - Removed dumb-init, not needed anymore - Some small shellcheck tweaks on the start/healthcheck scripts 2022-07-31 15:45:31 +02:00			`if [ -r "${f}" ]; then`
			`. "${f}"`
Add startup script to support init operations This is useful for making local customizations upon container start. To use this feature, mount a script into the container as `/etc/bitwarden_rs.sh` and/or a directory of scripts as `/etc/bitwarden_rs.d`. In the latter case, only files with an `.sh` extension are sourced, so files with other extensions (e.g., data/config files) can reside in the same dir. Note that the init scripts are run each time the container starts (not just the first time), so these scripts should be idempotent. 2020-07-06 00:26:20 +02:00			`fi`
			`done`
Remove warning when compiling only with mysql and add compatibility mode with the old docker script names 2021-04-29 15:58:29 +02:00			`elif [ -d /etc/bitwarden_rs.d ]; then`
			`echo "### You are using the old /etc/bitwarden_rs.d script directory, please migrate to /etc/vaultwarden.d ###"`
			`for f in /etc/bitwarden_rs.d/*.sh; do`
Update deps and Alpine image - Updated deps - Updated Alpine images to 3.16 - Removed dumb-init, not needed anymore - Some small shellcheck tweaks on the start/healthcheck scripts 2022-07-31 15:45:31 +02:00			`if [ -r "${f}" ]; then`
			`. "${f}"`
Remove warning when compiling only with mysql and add compatibility mode with the old docker script names 2021-04-29 15:58:29 +02:00			`fi`
			`done`
Add startup script to support init operations This is useful for making local customizations upon container start. To use this feature, mount a script into the container as `/etc/bitwarden_rs.sh` and/or a directory of scripts as `/etc/bitwarden_rs.d`. In the latter case, only files with an `.sh` extension are sourced, so files with other extensions (e.g., data/config files) can reside in the same dir. Note that the init scripts are run each time the container starts (not just the first time), so these scripts should be idempotent. 2020-07-06 00:26:20 +02:00			`fi`

Project renaming 2021-04-27 23:18:32 +02:00			`exec /vaultwarden "${@}"`