KeeWeb

KeeWeb is a password manager which supports managing kdbx files created by other applications such as KeePass, KeePassXC, etc. You choose the platform you wish to run; as KeeWeb supports being installed and ran as either a Desktop application, or in your web-browser. With support for Linux, Windows, and MacOS, we give you the tools to seamlessly manage your most important credentials across multiple applications and platforms. Decide how you want to save your credential vault, KeeWeb supports saving your database as a local file, or you can store your password vault with some of the most popular cloud services such as Dropbox, Google Drive, and Microsoft OneDrive. Apps Web, Desktop Try out our application Demos Web, Beta Test our stable and beta releases of Keeweb Services Favicon Grabber Services integrated within Keeweb Branches docker/alpine-base, docker/keeweb Important branches related to our project Timeline Release Notes, TODO See what we're planning On one page Features, FAQ Information about Keeweb development Website keeweb.info Visit our official website Social kee web Check us out on our social media Donate OpenCollective, GitHub Help keep us going Want to self-host your copy of KeeWeb? Everything you need to host this app on your server is provided within the package. KeeWeb itself is a single HTML file combined with a service worker (optionally; for offline access). Docker Compose For users wishing to use docker compose , create a new docker-compose.yml with the following: Traefik Integration You can put this container behind Traefik if you want to use a reverse proxy and let Traefik handle the SSL certificate management. If you do not use Traefik, you can skip this section of steps. This is only for users who wish to put this container behind Traefik. If you do not wish to use Traefik, remember that if you make your Keeweb container public facing, you will need to utilize a service such as certbot/lets encrypt to generate SSL certificates. Our first step is to tell Traefik about our Keeweb container. We highly recommend you utilize a Traefik dynamic file , instead of labels . Using a dynamic file allows for automatic refreshing without the need to restart Traefik when a change is made. To add Keeweb to Traefik, you will need to open your docker-compose.yml and apply the following labels to your Keeweb container. Ensure you change domain.lan to your actual domain name. After you've added the labels above, skip the dynamic.yml section and go straight to the static.yml section. Static.yml These entries will go in your Traefik static.yml file. Any changes made to this file requires that you restart Traefik afterward. This step is only for users who opted to use the dynamic file method. The code above is what enables the use of a dynamic file instead of labels. Change /etc/traefik/dynamic.yml if you are placing your dynamic file in a different location. This path is relative to inside the container, not your host machine mounted volume path. Traefik keeps most files in the /etc/traefik/ folder. After you add the above, open your Traefik's docker-compose.yml file and mount a new volume so that Traefik knows where your new dynamic file is: You must ensure you add a new volume like shown above: /config/dynamic.yml:/etc/traefik/dynamic.yml:ro On your host machine, make sure you place the dynamic.yml file in a sub-folder called config , which should be inside the same folder where your Traefik's docker-compose.yml file is. If you want to change this location, ensure you change the mounted volume path above. This step is required no matter which option you picked above, both for dynamic file setups, as well as people using labels . Open your Traefik static.yml file. We need to define the certResolver that we added above either in your dynamic file, or label. To define the certResolver , we will be adding a new section labeled certificatesResolvers . We are going to use Cloudflare in this example, you can