bw_web_builds VS HomeBrew

I upgraded to this: https://github.com/dani-garcia/bw_web_builds/releases/tag/v2023.2.0

downloaded the latest web vault release from https://github.com/dani-garcia/bw_web_builds, extracting it to the web-vault subdir,

The repository you are looking for is this one bw_web_builds. It basically checks out this official bitwarden repository and applies the patches under the /patches folder. It also has instructions for how to create your own patches by modifying the original repo and running a git diff command.

Dependencies required: brew (https://brew.sh/) postgreSQL: brew install postgresql nodejs12: brew install node@12 node-sass: brew install node-sass rust dev version: brew install rustup-init nginx: brew install nginx vaultwarden for macOS with postgreSQL ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ git clone https://github.com/dani-garcia/vaultwarden ./vaultwarden cd vaultwarden git checkout "$(git tag --sort=v:refname | tail -n1)" cargo build --features postgresql --release Congratulation, you have built a macOS binary for vaultwarden For web-vault (if you need it) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ git clone https://github.com/bitwarden/web.git web-vault cd web-vault Open a web browser and go to https://github.com/dani-garcia/bw_web_builds to see latest available patch for vaultwarden git checkout v2.20.4 git submodule update --recursive --init export WEB_VERSION=v2.20.4 curl https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/${WEB_VERSION}.patch >${WEB_VERSION}.patch git apply ${WEB_VERSION}.patch -v npm config set python /usr/local/bin/python3 npm install npm run dist Congratulation, you have built the web vault Post compile instructions ~~~~~~~~~~~~~~~~~~~~~~~~~ Vaultwarden binary can be found in the vaultwarden/target/release directory web-vault pack can be found in the vaultwarden/web-vault/build directory now you can create a "ditribution directory" where you want, for example: /data/vaultwarden /data/vaultwarden/web-vault and copy the binary directory with: cp -R PATH/vaultwarden/target/release/ /data/vaultwarden cp -R PATH/vaultwarden/web-vault/build/ /data/vaultwarden/web-vault modify PATH/vaultwarden/.env.template with the path and settings you want cp PATH/vaultwarden/.env.template /data/vaultwarden/.env To automatically start vaultwarden at boot (after powerfailure) create a plist in /Library/LaunchDaemons named vaultwarden.plist with this content and CHANGE change_username AND change_groupname to the user/group you want vaultwarden to be run as Label vaultwarden RunAtLoad KeepAlive UserName change_username GroupName change_groupname EnvironmentVariables PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin SHELL /bin/bash ProgramArguments /data/vaultwarden/vaultwarden WorkingDirectory /data/vaultwarden nginx proxy: server { if ($host = sub.example.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 10.0.1.2:80; server_name sub.example.com; } server { listen 443 ssl http2; server_name sub.example.com; ssl_certificate /data/letsencrypt/live/sub.example.com/fullchain.pem; # managed by Certbot ssl_certificate_key /data/letsencrypt/live/sub.example.com/privkey.pem; # managed by Certbot ssl_dhparam /data/letsencrypt/dhparams.pem; ssl_session_cache shared:SSL:10m; ssl_session_timeout 5m; add_header Alternate-Protocol 443:npn-spdy/3; add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"; ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers 'TLS-CHACHA20-POLY1305-SHA256:TLS-AES-256-GCM-SHA384:TLS-AES-128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256'; ssl_early_data on; ssl_ecdh_curve secp384r1; server_tokens off; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; add_header Referrer-Policy no-referrer-when-downgrade; add_header X-Frame-Options "SAMEORIGIN" always; ssl_stapling on; ssl_stapling_verify on; error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/local/opt/nginx/html; } location /robots.txt { return 200 "User-agent: *\nDisallow: /"; } location / { root /data/vaultwarden/web-vault; proxy_pass http://10.0.1.2:9000; client_max_body_size 100M; # Limit Document size to 100MB proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub/negotiate { root /data/vaultwarden/web-vault; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http://10.0.1.2:9000; } location /notifications/hub { root /data/vaultwarden/web-vault; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://10.0.1.2:3012; } } brew services restart nginx sudo launchctl load /Library/LauchDaemons/vaultwarden.plist Vaultwarden should be up and running

You can take a look at the latest patch file to see the changes from the official Bitwarden web vault. The main difference is probably that it now says "© 2021, Bitwarden Inc. (Powered by Vaultwarden)" in the footer.

Homebrew is a highly popular package manager on macOS and Linux systems, enabling users to easily install, update, and uninstall command-line tools and applications. Its design philosophy focuses on simplifying the software installation process on macOS, eliminating the need for manual downloads and compilations of software packages.

Homebrew - package manager for linux-based OSs.

Package Manager: Homebrew

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

Are you using SQLite that ships with macOS, or SQLite installed from homebrew?

I had a different problem in the past with the SQLite that ships with macOS, and have been using SQLite from homebrew since.

So if it’s the one that comes with macOS that gives you this problem that you are having, try using SQLite from homebrew instead.

https://brew.sh/

Before we begin, make sure you have Homebrew installed on your Mac. Homebrew is a package manager that makes it easy to install software and dependencies. You can install Homebrew by following the instructions on their website: https://brew.sh/

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

I have always either installed Node from the installer provided by the Nodejs website or, via Brew in macOS. I have also used nvm in the past but did not know that there was a best practice to guide us.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

On a macOS machine, you can use homebrew by running the command.