bitwarden_rs VS frp

org.opencontainers.image.documentationhttps://github.com/dani-garcia/bitwarden_rs/wiki

Bitwarden (Not officialy version), A password manager, provides browser extensions and clients on all platforms.

- use trusted images (for bitwarden i'm using bitwarden_rs , an unofficial Bitwarden server implementation written in Rust

https://github.com/dani-garcia/bitwarden_rs/issues/246#issuecomment-796966385

Bitwarden-rs

Bitwarden RS (https://github.com/dani-garcia/bitwarden_rs) running as addon in Home Assistant (Docker)

I have setup Bitwarden on my raspberry following Bitwarden_RS (https://github.com/dani-garcia/bitwarden_rs/wiki )using portainer docker manager instead of command line and setup frp server to connect my apps including Bitwarden which is hosted in my lan from internet

If you're okay with a third party solution, bitwarden_rs is a much lighter version of bitwarden that can run in docker

I have some loaded into my self-hosted Bitwarden RS, but that's definitely not my primary.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.

No, FRP - https://github.com/fatedier/frp

Another way around is to use reverse proxy like frp but since you need SSH anyway, all you need is already comes with SSH (reverse SSH)

Take a look also onto popular, similar to yours project: frp

You may want to take a look at FRP. It’s the same idea like Cloudflare tunnel, just without all the sophisticated features. You put a server (frps) on a VPS with public IP, and a client (frpc) within your home NAT. It can do both TCP and HTTP reverse proxy. I recommend a simple TCP one, and let your local nginx handle SSL.