why no X11?

Because everyone's going for Wayland, even though you still need XWayland to do anything useful on it because Wayland is comically incomplete.

well, I mean, why can't this ship with an X server? Or maybe it does and then I'm not sure why it is said that only Haiku apps are supported

It's not that it can't, if you can do something it doesn't mean you should. If we used X it'd be another linux distro isn't it? Part of the fun is to make your own UI feel.

For my daily machine, I need Docker, terminal, Firefox (for private browsing), Chrome (for work), VS Code and/or JetBains IDE. If this can feel a bit like I remember BeOs felt, that'd be awesome

Brilliant way to expose your company's secret data on the Internet :-)

you can put your password to a yubikey, then it's always a long press of a button away

BTW, you can also enable the PW feedback on the classic sudo. I've done that on one of my hosts

I tried using this to handle my 10-ish Docker containers, but I ended up using Portainer. Sure, not the same thing, but if someone (like me) thought Cockpit might be nice for managing a small Docker host, this didn't work for me

Going for a shameless plug - I am working on an observability dashboard for Docker Swarm: https://github.com/Radiergummi/cetacean

Also works for a single node cluster. Maybe that’s closer to what you’re looking for.

Hey that’s pretty cool, nice to see someone paying attention to Docker Swarm (it’s nice for simple deployments, like multi-server Compose). You might want to add some screenshots to the docs though.

There was also Swarmpit but it didn’t really get that much love, sadly: https://github.com/swarmpit/swarmpit/issues/719

Portainer is pretty nice feature wise but even with lowered MTU I still get odd networking related issues (seems like the agent or whatever cannot reach the manager sometimes) but I’ve had those sorts of issues across multiple different clusters, both in cloud and on-prem with single leader setups and across both RPM and DEB only clusters. Weird stuff, otherwise perhaps the most established solution for Docker Swarm.

Yeah, I was a long time Swarmpit user, but as you said it’s abandoned, has lots of unfixed bugs, and is pretty heavy. So I set out to build something light on Go to replace it.

I love swarm! If only it wasn’t the unloved step child…

Thanks for this, going to check it out now

can you please add some screenshots?

Yeah, fair point, I didn't get to that yet. Here's a bunch from my current development state:

https://imgur.com/a/KhgTg6Y

I ended up on this journey using Dockge. Inoffensive and you can stick your compose files in a directory and manage with git vs. Portainer’s attempt to hide them.

What you're looking for is Dokploy. It's much better than it's predecessors like Dokku, CapRover, etc.

I was heavily impressed with CapRover 5 years ago, so if you’re right, it’s worth checking this out.

Agree. Dokploy is pretty good solution overall.

I think what the comment meant was that it's harder for an individual to lose their paper documents compared to losing the electronic ones. It just shifts who's responsible for keeping them safe

Can use AI to detect that

not per capita though

Makes it easier to parse by automatic tools too