Oxidized VS vaultwarden

after using expect and TCL heavily for years, I can firmly say they suck at scale.

Ruby https://github.com/ytti/oxidized/blob/master/lib/oxidized/mo...

Oxidized supports PFSense natively - https://github.com/ytti/oxidized/blob/master/lib/oxidized/model/pfsense.rb

Oxidized? https://github.com/ytti/oxidized

Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized

Check out Oxidized

You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email.

To people who want to self-host this, look at Vaultwarden which is a fully compatible alternate server with even more features:

https://github.com/dani-garcia/vaultwarden

Been running it for a year with 0 issues.

For passwords and 2FA I use Bitwarden in combination with a self-hosted Vaultwarden service (for imcreased security and use of pro features for free).

Vaultwarden as Password-Safe

I have a lot of software that I host myself on my home server, partly to save money but also because I want to control my own data. For example, I host VaultWarden which is the open source server for BitWarden. This gives me all the premium features for free with the added bonus of keeping my passwords out of the cloud.

Self hosting is incredibly easy with vaultwarden (https://github.com/dani-garcia/vaultwarden)

I have now switched to using the BitWarden app with the self-hosted VaultWarden server. I have set it up, so my passwords are only accessible when connected to my home network either physically or with a VPN (I am using tailscale for this).