TDP is a very misunderstood concept these days because it used to be a hard upper limit but now it’s god knows what. The Spec Sheet is calling it “Processor Base Power”. What might that be you ask? Well of course it is

The time-averaged power dissipation that the processor is validated to not exceed during manufacturing while executing an Intel-specified high complexity workload at Base Frequency and at the junction temperature as specified in the Datasheet for the SKU segment and configuration.

In other words it’s just marketing mumbo jumbo. According to other users the N150 can draw as much as 20 up to 35 watts even. The fact that the heat is radiating well through your case sounds like a positive if anything. This is x86 we’re talking about. The added complexity of that architecture over ARM comes at a price.

You’re making a valid point. fwiw I wasn’t trying to advocate for my approach as a best practice I was just saying this is my reality thus far. (I think I’ve been on Vaultwarden for about 2 years now.)

Watchtower itself basically just does “docker pull + down + up” for you, so whether that recreation of the container and any necessary migration work out is up to the software inside. One essential part of my infrastructure that I can think of where breaking changes did necessitate manual intervention was wg-easy my Wireguard container. But that just meant that I was stuck on an outdated version until I transitioned my compose file to get the new stuff. I can’t remember anything ever breaking through an unattended Watchtower update, which maybe I shouldn’t be saying out loud but oh well.

Thanks for the reply. So what kind of magnitude are we talking on the RAM usage here? Some people here talked about not being able to fit it inside 2G total. So I assume it’s probably like hundreds of megs which is only really significant in such low memory configurations.

It’s a completely fair standpoint. You have to look out for your business first. I’m just the sysadmin trying to weigh some counterpoints because I deal with threat aversion and infrastructure hardening on a day-to-day basis.

Once one has a solution that’s at least good enough people will usually stick with that, which is also fair. I know that the decisionmakers who pay my salary can’t have me follow every tech lead where my hourly wage goes to something that’s not a direct moneymaker.

That was the red flag for me personally in terms of giving it a try. At the first accusation they said “the code is there, I have nothing to hide” (which is entirely fair) but then it devolved into (paraphrasing) “I took down issue reporting because people kept abusing it.”

So assuming the best case scenario where the code is clean and it’s just a misunderstanding you’re still looking at a creator who is willing to censor the community they simultaneously seem particularly eager to reach by self-promoting their project. Not my jam.

For how long and how do resource usage and storage space used look by now?

Like I said in my other comment, Vaultwarden is probably not something you could set up yourself but it would basically give you the paid featureset of Bitwarden within all the Bitwarden apps and browser plugins at zero cost or whatever hosting it in the cloud would cost you.

Personally I’d rather have my (albeit thoroughly encrypted) password data on hardware that I control than giving it to someone else. Data sovereignty is something you can’t really “buy” into. Whether your company can justify paying a freelancer or some specialist to do the initial setup is a different question which I think can be answered while imagining a worst case scenario of a company like Bitwarden or 1Password getting hacked. Passwords are never stored in plaintext of course but things like personal or credit card data for example can still get compromised when using a readymade subscription.

Interesting that the current version has this bug. I think around the time I started using Vaultwarden as my Bitwarden backend it was also said that the password-sharing should be treated as experimental, but I have had zero issues with it so far. The Web UI might not be super self-explanatory the first time round when it comes to sharing passwords with others but I mean as far as I know this is the work of a single Bitwarden-employee doing this in their free time. And once you have the org set up you don’t have to rely on the Web UI for any of the sharing, transferring, creating and whatnot anymore.

If it is currently impossible to create new Organizations then I’m sure this week-old bug will be resolved fairly soon, probably with the next release.

Either way OP said they’re not tech-savvy so they would probably need to hire someone to set this up for them, which I wouldn’t say is a ludicrous thing to suggest. Even with the level of encryption that this data is stored with you can never go wrong with the data sovereignty that comes with self-hosting. Once you have Vaultwarden in a Docker container with Watchtower updating it regularly it’s zero maintenance as far as I’m concerned.

I don’t necessarily sync my dotfiles across machines, at least not in a blanket fashion. But I use Seafile to keep all sorts of directories in sync across machines. It’s basically a self-hostable Dropbox.

The fact that ISPs can do this should be a fkn outrage. But this is so far removed from what people care about. And so net neutrality gets eroded.