I used to run dockprom but it was pretty ressource intensive and I have since moved to Beszel + Uptime Kuma.

I have yet to find a way to keep logs between container re-creation (I unsuccessfully tried to set up Loki back when I ran dockprom), both Beszel and Komodo only display logs from the container currently running in the stack.

I have no idead if or where LLM’s are being used

Having read previous Bluefin announcements, the Bluefin maintainers have fully embraced LLMs, so I wouldn’t be surprised if they made extensive use of them for Bluefin Server.

Personally, I would put one of the 990 in the server, use it as system drive + storage for databases and such. Then, the EVO in NAS to store backups, as it’s not very bandwidth sensitive and saves a little bit of lifespan out of the main SSD. And probably an extra copy of your restic repository onto the external 2TB SSD (though I would store that extra backup offsite on Backblaze B2)

Oh, and you should probably set up restic’s rest-server, it makes backuping from other computers really easy (easier than SFTP, which I had issues with)

and probably everything else too

*Takes a look at the top three folders*

• .agents/skills
• .claude/skills
• .cursor/rules

Yep…

I read lots of comments comparing the price tag to the Quest 2/3, but you all seem to forget that the Quest was heavily subsidised by Meta.

I also have it, I find it quite tricky to work in it because of its compactness. In retrospect, I would have gone with a Fractal Design Define and some hack to enable drives hot swap.

What’s your issue exactly?

Personally, I set up Caddy with subdomains like radarr.local.example.tld, added a DNS entry on my domain so that *.local.example.tld points to the local IP of Caddy, then followed this guide so that Caddy issues TLS certificates using the DNS challenge (since the subdomains don’t point to anything accessible from Internet) along with the caddy-docker-proxy plug-in to easily manage upstreams.