Vaultwarden isnt a fork because bitwarden isn’t selfhostable. Bitwarden has an official selfhosted version. Vaultwarden is a lightweight rust version of the backend. As the selfhosted version by bitwarden is quite fat. Vaultwarden uses the official webapp of the webvault in their fork.

You can reference a single or multiple containers in a compose stack.

docker compose -f /path/to/compose.yml restart NameOfServiceInCompose

Just for clarification: https://wikipedia.org/wiki/Cryptographic_nonce

No it’s not suspicious. It’s an open source well vetted audited selfhosted password manager. If youve tried vaultwarden or the official image it’s extremely easy to setup meaning a very low barrier for entry.

Na IPv6 goes back to what ipv4 was when there isn’t a public and private range. Private ranges were due to ip exhaustion. NAT is then used.

With ipv6 you subnet your Lan with ipv6 delegate range from your ISP. Basically it’s like subnetting your lan with a public ipv4 range. No nat required. As a firewall is used to stop packets not NAT. Also ipv4 RFC1918 doesn’t provide a few thousand for private, it provides 17 million.