vaultwarden/docker/start.sh

#!/bin/sh

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 01:26:20 +03:00			`#!/bin/sh`

Project renaming 2021-04-28 00:18:32 +03: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 16:58:29 +03: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 01:26:20 +03:00			`fi`

Project renaming 2021-04-28 00:18:32 +03:00			`if [ -d /etc/vaultwarden.d ]; then`
			`for f in /etc/vaultwarden.d/*.sh; do`
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 01:26:20 +03:00			`if [ -r $f ]; then`
			`. $f`
			`fi`
			`done`
Remove warning when compiling only with mysql and add compatibility mode with the old docker script names 2021-04-29 16:58:29 +03: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`
			`if [ -r $f ]; then`
			`. $f`
			`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 01:26:20 +03:00			`fi`

Project renaming 2021-04-28 00:18:32 +03:00			`exec /vaultwarden "${@}"`