Yeah, I recalled that for-real Bitwarden uses dotnet and mssql so I'm sure Digital Ocean loves the situation where someone needs a huge instance
I was curious given the mention of "docker-compose" how exactly that worked (did it have them set with "restart: always" and similar operational sanity?) but while digging into it:
Having a self-modifying script that curls from some malware-looking domain defeats the purpose of having tagged scripts, doesn't it? https://github.com/bitwarden/server/blob/v1.48.1/scripts/bit...
Don't worry, even the redirected "self-host" version does the same trick for inexplicable reasons: https://github.com/bitwarden/self-host/blob/master/bitwarden...
I never found the docker-compose files, so I guess they're emitted as a side-effect of running the "bitwarden/setup" docker image or something: https://github.com/bitwarden/self-host/blob/master/run.sh#L1...
I recommend using vaultwarden instead to self-host bitwarden: https://github.com/dani-garcia/vaultwarden
https://github.com/bitwarden/server/blob/master/util/Setup/T...
Does it checks the memory and fails with a message? What could possibly be done by a password-storing app that requires 2GB of RAM?
Compose template for the setup component is here: https://github.com/bitwarden/server/blob/master/util/Setup/T...
