37 Commits

Author SHA1 Message Date
4bb0a87b33 increase healthcheck retries
Some checks failed
continuous-integration/drone/push Build is failing
2025-12-23 14:48:53 +01:00
22c3dbb9b8 chore: publish 2.1.1+1.34.3 release
Some checks reported errors
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build was killed
2025-11-27 10:39:49 +01:00
3wc
74861fd9de chore: publish 2.1.0+1.34.1 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2025-06-18 18:15:58 +01:00
6b47b3d040 Merge pull request 'add solution to missing argon2 error message' (#11) from argon2-doc into main
All checks were successful
continuous-integration/drone/push Build is passing
Reviewed-on: #11
2025-05-05 22:24:06 +00:00
3b2f17908f add solution to missing argon2 error message 2025-05-03 21:19:36 +00:00
681d84009e Merge pull request 'fix: don't enable SMTP by default' (#9) from smtp-not-enabled-by-default into main
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
Reviewed-on: #9
2025-04-24 08:11:44 +00:00
426c0c026f fix: don't enable SMTP by default
See #8
2025-04-24 09:50:47 +02:00
0c8a4ddc50 Merge pull request 'fix: set umask closes #6' (#7) from issue-6 into main
All checks were successful
continuous-integration/drone/push Build is passing
Reviewed-on: #7
Reviewed-by: decentral1se <decentral1se@noreply.git.coopcloud.tech>
2025-04-23 19:21:16 +00:00
f
cab11b0e2a fix: remove world access to existing data 2025-04-03 17:06:53 -03:00
f
938e4671b4 fix: set umask closes #6 2025-03-31 15:40:03 -03:00
96c7c18029 chore: publish 1.1.0+1.33.2 release 2025-02-24 14:49:03 +01:00
936d2c7044 add timezone env TX 2025-02-24 14:44:41 +01:00
705f81dfb2 add release notes for older version with upgrade warning
All checks were successful
continuous-integration/drone/push Build is passing
2025-01-20 14:25:52 +01:00
913b973b6b chore: publish 1.0.4+1.32.7 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2025-01-20 13:18:20 +01:00
9e66edca72 increase entrypoint version which was missing from last modification. (last 4 releases are not upgradeable)
All checks were successful
continuous-integration/drone/push Build is passing
2025-01-20 13:06:22 +01:00
40d49eb4c3 Update .drone.yml
Some checks failed
continuous-integration/drone/push Build is failing
2025-01-08 10:09:13 -08:00
6cf7412473 chore: publish 1.0.3+1.32.5 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2024-12-16 15:47:27 +01:00
20ddaec548 patch vaultwarden backup label 2024-12-16 15:47:02 +01:00
e29a5a9ce3 chore: publish 1.0.2+1.32.5 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2024-12-16 15:25:15 +01:00
3274ef6feb fix mariadb backupbot label
All checks were successful
continuous-integration/drone/push Build is passing
2024-12-16 15:23:28 +01:00
c48778f942 chore: publish 1.0.1+1.32.5 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2024-12-10 18:34:31 +01:00
d52c9d220e chore: publish 1.0.0+1.32.3 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2024-12-10 18:26:46 +01:00
7de85bb0b5 add optional mariaDB and provide function for hashing the admin_token 2024-12-10 18:25:19 +01:00
3wc
2c76e6640f chore: publish 0.9.1+1.32.3 release
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2024-10-30 13:39:53 -04:00
b286befb98 Added extra steps to quickstart in README
All checks were successful
continuous-integration/drone/push Build is passing
2024-10-07 16:30:25 +01:00
b47b82d15a Merge pull request 'Define $COMPOSE_FILE in config to fix abra app deploy error' (#3) from marlon/vaultwarden:main into main
All checks were successful
continuous-integration/drone/push Build is passing
Reviewed-on: #3
Reviewed-by: decentral1se <decentral1se@noreply.git.coopcloud.tech>
2024-09-28 10:57:32 +00:00
b0d701b0e8 Define $COMPOSE_FILE in config to fix abra app deploy error
By default, the config options provided in the template fail because $COMPOSE_FILE is not set, leading to an error `[abra recipe path] is a directory` when running `abra app deploy`. This is fixed by setting `$COMPOSE_FILE` to `compose.yml`
2024-09-20 13:59:25 +00:00
7f60d33d21 chore: publish 0.9.0+1.32.0 release
All checks were successful
continuous-integration/drone/push Build is passing
2024-08-26 18:07:07 +01:00
57a40cfaa1 chore: publish 0.8.0+1.31.0 release
All checks were successful
continuous-integration/drone/push Build is passing
2024-07-19 18:55:59 +02:00
373db38548 feat: add smtp support
All checks were successful
continuous-integration/drone/push Build is passing
2024-07-09 15:37:09 +02:00
4c50e82865 chore: publish 1.2.0+1.30.5 release
All checks were successful
continuous-integration/drone/push Build is passing
2024-03-18 15:00:09 +00:00
06c0d8ffd4 chore: publish 1.1.0+1.30.5 release 2024-03-18 14:55:49 +00:00
371fa36d15 chore: publish 1.0.0+1.30.5 release 2024-03-18 14:54:20 +00:00
c3dbb3e4dd chore: publish 0.7.2+1.30.3 release
All checks were successful
continuous-integration/drone/push Build is passing
2024-02-13 17:50:11 +01:00
3wc
8ef06543d2 chore: publish 0.7.1+1.30.1 release
All checks were successful
continuous-integration/drone/push Build is passing
2023-11-20 12:55:18 +00:00
c59446cca2 Merge pull request 'add config for backup command' (#2) from p4u1/vaultwarden:enable-backup into main
Some checks reported errors
continuous-integration/drone/push Build encountered an error
Reviewed-on: #2
2023-11-06 23:11:14 +00:00
88210401bd add config for backup command 2023-11-06 21:26:00 +01:00
14 changed files with 181 additions and 9 deletions

View File

@ -34,7 +34,7 @@ steps:
from_secret: drone_abra-bot_token
fork: true
repositories:
- coop-cloud/auto-recipes-catalogue-json
- toolshed/auto-recipes-catalogue-json
trigger:
event: tag

View File

@ -3,6 +3,8 @@ TYPE=vaultwarden
DOMAIN=vaultwarden.example.com
LETS_ENCRYPT_ENV=production
COMPOSE_FILE="compose.yml"
WEBSOCKET_ENABLED=true
SIGNUPS_ALLOWED=true
@ -12,3 +14,20 @@ LOG_FILE=/data/vaultwarden.log
LOG_LEVEL=warn
SECRET_ADMIN_TOKEN_VERSION=v1 # length=48
TX="Europe/Berlin"
## DB settings
#COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
#SECRET_DB_PASSWORD_VERSION=v1
#SECRET_DB_ROOT_PASSWORD_VERSION=v1
## SMTP settings
#COMPOSE_FILE="$COMPOSE_FILE:compose.smtp.yml"
#SECRET_SMTP_PASSWORD_VERSION=v1
#SMTP_ENABLED=1
#SMTP_FROM=noreply@example.com
#SMTP_USERNAME=noreply@example.com
#SMTP_HOST=mail.example.com
#SMTP_PORT=587
#SMTP_SECURITY=starttls

View File

@ -8,8 +8,8 @@
* **Status**: 2, beta
* **Image**: [`vaultwarden/server`](https://hub.docker.com/vaultwarden/server), 4, upstream
* **Healthcheck**: 3
* **Backups**: No
* **Email**: No
* **Backups**: Yes
* **Email**: Yes
* **Tests**: No
* **SSO**: No
@ -21,6 +21,8 @@
2. Deploy [`coop-cloud/traefik`]
3. `abra app new vaultwarden`
4. `abra app config YOURAPPDOMAIN`
5. `abra app cmd -l YOURAPPDOMAIN insert_vaultwarden_admin_token` will insert a hashed `admin_token` as password as recommended by vaultwarden. Will echo the admin_token to your cli.
6. `abra app secret insert YOURAPPDOMAIN smtp_password v1 "super-secret-password"` SMTP config and password needed for user email invites
5. `abra app deploy YOURAPPDOMAIN`
[`abra`]: https://git.coopcloud.tech/coop-cloud/abra
@ -28,6 +30,9 @@
## Tips & Tricks
### Using MariaDB instead of SQLite
Just comment in the `DB settings` section in your .env
### Wiring up `fail2ban`
You need the following logging config:

23
abra.sh
View File

@ -1,6 +1,27 @@
export APP_ENTRYPOINT_VERSION=v1
export APP_ENTRYPOINT_VERSION=v4
APP_DIR="app:/data"
insert_vaultwarden_admin_token() {
if ! command -v argon2 &> /dev/null; then
echo "argon2 is required on your local machine to hash the admin token."
echo "It could not be found in your PATH, please install argon2 to proceed."
echo "For example: On a debian/ubuntu system, run `apt install argon2`"
exit 1
fi
PASS=$(openssl rand 64 | openssl enc -A -base64)
# -e: output encoded hash, -id: use Argon2id, -k: memory cost, -t: time cost, -p: parallelism
HASH=$(echo -n "$PASS" | argon2 "$(openssl rand -base64 32)" -e -id -k 65540 -t 3 -p 4)
if abra app secret insert -C "$APP_NAME" admin_token v1 "$HASH"; then
echo "Vaultwarden Admin Token is:"
echo "$PASS"
echo "TAKE NOTE OF IT NOW, WILL NEVER BE SHOWN AGAIN!"
else
echo "Failed to insert admin token."
exit 1
fi
}
_backup_app() {
# Copied _abra_backup_dir to make UX better on restore and backup
{

51
compose.mariadb.yml Normal file
View File

@ -0,0 +1,51 @@
---
version: "3.8"
services:
app:
environment:
# DATABASE_URL with secret db_password is being set by entrypoint.sh.tmpl
- MYSQL_HOST=db
- MYSQL_DATABASE=vaultwarden
- MYSQL_USER=vaultwarden
- MYSQL_PASSWORD_FILE=/run/secrets/db_password
secrets:
- db_password
db:
image: "mariadb:10.11" # or "mysql"
environment:
- MYSQL_DATABASE=vaultwarden
- MYSQL_USER=vaultwarden
- MYSQL_PASSWORD_FILE=/run/secrets/db_password
- MYSQL_ROOT_PASSWORD_FILE=/run/secrets/db_root_password
- MAX_DB_CONNECTIONS=${MAX_DB_CONNECTIONS:-100}#
secrets:
- db_root_password
- db_password
volumes:
- "mariadb:/var/lib/mysql"
networks:
- internal
deploy:
labels:
backupbot.backup.pre-hook: 'mysqldump --single-transaction -u root -p"$$(cat /run/secrets/db_root_password)" $${MYSQL_DATABASE} > /var/lib/mysql/backup.sql'
backupbot.backup.volumes.mariadb.path: "backup.sql"
backupbot.restore.post-hook: 'mysql -u root -p"$$(cat /run/secrets/db_root_password)" $${MYSQL_DATABASE} < /var/lib/mysql/backup.sql'
healthcheck:
test: ["CMD-SHELL", 'mysqladmin -p"$$(cat /run/secrets/db_root_password)" ping']
interval: 30s
timeout: 10s
retries: 30
start_period: 1m
secrets:
db_root_password:
external: true
name: ${STACK_NAME}_db_root_password_${SECRET_DB_ROOT_PASSWORD_VERSION}
db_password:
external: true
name: ${STACK_NAME}_db_password_${SECRET_DB_PASSWORD_VERSION}
volumes:
mariadb:

20
compose.smtp.yml Normal file
View File

@ -0,0 +1,20 @@
---
version: "3.8"
services:
app:
secrets:
- smtp_password
environment:
- "SMTP_ENABLED"
- "SMTP_PASSWORD_FILE=/run/secrets/smtp_password"
- "SMTP_FROM"
- "SMTP_USERNAME"
- "SMTP_HOST"
- "SMTP_PORT"
- "SMTP_SECURITY"
secrets:
smtp_password:
external: true
name: ${STACK_NAME}_smtp_password_${SECRET_SMTP_PASSWORD_VERSION}

View File

@ -3,9 +3,10 @@ version: "3.8"
services:
app:
image: vaultwarden/server:1.30.0
image: vaultwarden/server:1.34.3
networks:
- proxy
- internal
environment:
- "DOMAIN=https://$DOMAIN"
- "WEBSOCKET_ENABLED=$WEBSOCKET_ENABLED"
@ -15,11 +16,13 @@ services:
- "EXTENDED_LOGGING=$EXTENDED_LOGGING"
- "LOG_FILE=$LOG_FILE"
- "LOG_LEVEL=$LOG_LEVEL"
- "TX=${TX:-Europe/Berlin}"
configs:
- source: app_entrypoint
target: /docker-entrypoint.sh
mode: 0555
entrypoint: /docker-entrypoint.sh
# entrypoint: ['tail', '-f', '/dev/null']
command: /start.sh
secrets:
- admin_token
@ -27,9 +30,10 @@ services:
- vaultwarden_data:/data
healthcheck:
test: curl -f http://localhost/alive || exit 1
interval: 5s
timeout: 3s
retries: 10
interval: 30s
timeout: 10s
retries: 30
start_period: 1m
deploy:
restart_policy:
condition: on-failure
@ -39,7 +43,9 @@ services:
- "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`)"
- "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
- "coop-cloud.${STACK_NAME}.version=0.7.0+1.30.0"
- "coop-cloud.${STACK_NAME}.version=2.1.1+1.34.3"
- "backupbot.backup=true"
- "backupbot.backup.path=/data"
volumes:
vaultwarden_data:
@ -47,6 +53,7 @@ volumes:
networks:
proxy:
external: true
internal:
configs:
app_entrypoint:

View File

@ -1,6 +1,24 @@
#!/bin/bash
set -e
umask 027
# set DATABASE_URL with db_password
set_db_url() {
if test -f "/var/run/secrets/db_password"; then
pwd=`cat /var/run/secrets/db_password`
if [ -z $pwd ]; then
echo >&2 "error: /var/run/secrets/db_password is empty"
exit 1
fi
echo "entrypoint.sh setting DATABASE_URL"
export "DATABASE_URL"="mysql://vaultwarden:${pwd}@db/vaultwarden"
unset "pwd"
else
echo >&2 "error: /var/run/secrets/db_password does not exist"
exit 1
fi
}
file_env() {
local var="$1"
@ -24,8 +42,19 @@ file_env() {
unset "$fileVar"
}
if [ -n "${MYSQL_HOST}" ]; then
set_db_url
fi
file_env "ADMIN_TOKEN"
{{ if eq (env "SMTP_ENABLED") "1" }}
file_env "SMTP_PASSWORD"
{{ end }}
# remove world permissions on data
chmod -R o= /data
# upstream startup command
# https://github.com/dani-garcia/vaultwarden/blob/60ed5ff99d15dec0b82c85987f9a3e244b8bde91/docker/Dockerfile.j2#L254
/start.sh

1
release/1.0.0+1.32.3 Normal file
View File

@ -0,0 +1 @@
ATTENTION: this version is not automatically upgradeable due to missing entrypoint version increase. Please upgrade to at least 1.0.4+1.32.7 directly.

1
release/1.0.1+1.32.5 Normal file
View File

@ -0,0 +1 @@
ATTENTION: this version is not automatically upgradeable due to missing entrypoint version increase. Please upgrade to at least 1.0.4+1.32.7 directly.

1
release/1.0.2+1.32.5 Normal file
View File

@ -0,0 +1 @@
ATTENTION: this version is not automatically upgradeable due to missing entrypoint version increase. Please upgrade to at least 1.0.4+1.32.7 directly.

1
release/1.0.3+1.32.5 Normal file
View File

@ -0,0 +1 @@
ATTENTION: this version is not automatically upgradeable due to missing entrypoint version increase. Please upgrade to at least 1.0.4+1.32.7 directly.

1
release/1.0.4+1.32.7 Normal file
View File

@ -0,0 +1 @@
bugfix release for missing increase of entrypoint version for the last 4 releases. Also upgraded vaultwarden bugfix release.

15
release/2.0.0+1.33.2 Normal file
View File

@ -0,0 +1,15 @@
=== SMTP SETTINGS ===
This release contains a *breaking change* if you use SMTP with vaultwarden.
See https://git.coopcloud.tech/coop-cloud/vaultwarden/pulls/9 for more.
TLDR; Please add `SMTP_ENABLED=1` to your .env to continue using SMTP.
=== PERMISSIONS ===
Previously, the data directory including the main private key had read
permissions enabled for all host users. This release fixes that. Please review
your Vaultwarden keys if other users on your Co-op Cloud host may have had
access to these files.
See https://git.coopcloud.tech/coop-cloud/vaultwarden/pulls/7 for more.