adding untested changes and new dockers

tools/vaultwarden/.env.example

@@ -0,0 +1,2 @@
+SIGNUPS_ALLOWED=false
+INVITATIONS_ALLOWED=true

tools/vaultwarden/README.md

@@ -0,0 +1,5 @@
+# Bitwarden but vaultwarden
+
+This is bitwarden, it's compatible with any bitwarden extension or software, it's just made in rust, generally takes less resources and doesn't scale as well, good for ~50 people(guess)
+
+Configurations by default disable registration and enable them by invitations, change to enable to create the first one and change back to only allow by invitation

tools/vaultwarden/docker-compose.yml

@@ -0,0 +1,13 @@
+services:
+    vaultwarden:
+        image: vaultwarden/server:latest
+        container_name: vaultwarden
+        restart: always
+        environment:
+            # DOMAIN: "https://vaultwarden.example.com"  # required when using a reverse proxy; your domain; vaultwarden needs to know it's https to work properly with attachments
+            SIGNUPS_ALLOWED: ${SIGNUPS_ALLOWED} # Deactivate this with "false" after you have created your account so that no strangers can register
+            INVITATIONS_ALLOWED: ${INVITATIONS_ALLOWED}
+        volumes:
+            - ./data:/data # the path before the : can be changed
+        ports:
+            - 8081:80 # you can replace the 11001 with your preferred port