As much as I dislike UniFi, it is true that there isn’t really a competitor in their tier of equipment. Upgrading would be a good choice, but if you end up choosing to stay with UniFi, I’d highly recommend the UCGs.

The UDR and UDM line are so horrifically poorly designed it’s frankly astonishing they ever left the drawing board. Not only is the shape unwieldy and awkward enough on its own, the thermals on those things are terrible. I used to wake up to no internet every few weeks because my UDM would overheat and would be unable to boot until you cooled it down. I learned to just stick it in the fridge for a bit to cool it down so it could boot again.

The UniFi UCG ultra and the Max are far better machines, capable of doing just as much if not more than the Pill shaped routers while staying cool and not sounding like a jet engine every time you send a text over wifi. The only thing you even lose is the integrated Access Point which sucks compared to the discrete ones anyway.

This will happen automatically if you buy enough and start experiencing their true hardware failure rate lol.

Reading between the lines I feel like when you say “Targeted towards self hosters” what you mean is “John Q Hobbyist who doesn’t know any better”

And in response to that I would contend that Gitea is not actually targeted at those folks, though they obviously use it. Gitea is FOSS but it’s still “targeted” at professionals.

It was not

Yeah but Umami is an analytics engine powered by client side tracking. If it was behind a VPN it would be useless.

I don’t know about “all umami instances being infected” but they were certainly all vulnerable.

When you say AI, do you mean you’re vibe coding this, or like you’re using AI as a learning tool?

You’re right about that.

I do sometimes miss PlexAmp, but the native Emby application for music on iOS is pretty decent. Just kinda wish it was decoupled from the main app.

They both suck pretty bad

You are correct, Dokploy and Coolify are both listed as inspirations for ZaneOps.

lol not quite but I catch your drift.

Portainer is a container management system. It’s purpose is to allow you to manage containers in an easy to use GUI.

ZaneOps is a PaaS that allows you to automatically build and deploy web apps into containers without having to configure the underlying infrastructure at all.

For example, to deploy my static site on Portainer, I’d have to build my static site, containerize it, upload the container image to a registry (or directly to Portainer), then use Portainer to configure the environment and deploy the container. Then I’d have to configure a reverse proxy or web server to serve the contents of the container. If I wanted to continue working on that static site I’d need to configure some kind of CI/CD pipeline to try and automate all that previous work.

With ZaneOps, I store the Astro/11ty/other SSG files in a Git repo, and on any commit ZaneOps will automatically recognize the SSG framework I’m using, use Docker Swarm to spin up a container to build the site into static files, containerize the resulting files for me, and deploy the container. It then uses Caddy underneath to serve what’s in the container including provisioning SSL certs for the site. It will health check the new container before deploying it in a blue/green deployment model so that the old site is removed only after the new one is up and available. It’s the same workflow as deploying a site to GitHub Pages using GitHub Actions if you’ve ever done that.

Ultimately. You end up with the same result, a containerized workload, but ZaneOps takes your GitHub Repo and turns it into a built, running, containerized workload automatically. Automating the deployment of my own web apps using Portainer would be at the very least clunky and require a lot of surrounding infrastructure. It’s not something Portainer just does out of the box.

Cockpit isn’t much like either, it’s just a web based server management tool.

Nothing. Just helps pay for development.

Wasn’t it stable like a month ago?

This was the peak of human civilization.

Like being able to return games? That was to comply with an Australian law, and it was just easier to implement it for everyone than just do it for Australia specifically.

Well you say that but Sony also has an online game marketplace that operates in Australia.

I don’t know how it works in Australia, but in the U.S. their return policy is not nearly as generous as Steam’s. In fact it Sony’s return policy only really exists on paper. In reality they don’t really do returns at all.

Yes and it’s so funny to me as somebody that works in datacenter and cloud infrastructure for public apps for a living. All the gatekeeping is done by hobbyists without the faintest clue but all the confidence in the world, or click ops internal IT sysadmins grossly overestimating their self worth.

Be safe, ask questions, and fuck what the haters think.

On the contrary, lots of us write our own scripts and programs. And when considering how to self host that software, serverless is a perfectly valid choice.

Just because many self hosters are hobbyists who are only capable of using things off the shelf doesn’t make self hosting infrastructure outside the scope of… selfhosting lol

Why wouldn’t serverless technologies be relevant to the self hosted community?