Live data from Hacker News

Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

github.com

11–20 of 149 posts

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#11
This is really neat! I'm working a message queue in go (drop-in replacement for SQS) and also thinking about autoscaling. I've been playing with raft vs using a central store (ie, postgres) to coordinate.

Can you tell me more about IPFS - I've never used it before. How has that been working, and can you tell me what you've observed when you have many nodes which need to coordinate?

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#12

What's with the vilification of kubernetes? 99% of this document ( https://tau.how/99-Misc/kubernetes/01-k8s-cons/ ) boils down to "You have to understand what a pod, deployment, container, etc is" once you remove every line that discusses the cons of managing a cluster yourself, because nobody actually does that except extremely large orgs. All of these problems go away when you utilize a managed offering like DOKS,…

If your goal is to self-host your own PaaS, why would you use a managed k8s offering?

Why wouldn't you? If you decide to not use a PaaS and self host your own servers would you reach for a VPS or would you manage your own rack in a colocated data center?

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#13

What's with the vilification of kubernetes? 99% of this document ( https://tau.how/99-Misc/kubernetes/01-k8s-cons/ ) boils down to "You have to understand what a pod, deployment, container, etc is" once you remove every line that discusses the cons of managing a cluster yourself, because nobody actually does that except extremely large orgs. All of these problems go away when you utilize a managed offering like DOKS,…

If your goal is to self-host your own PaaS, why would you use a managed k8s offering?

"Self-hosting" doesn't necessarily mean you own the hardware. Many people self-host on cloud providers at different levels (Fly, Digital Ocean/Hetzner, GCP/Azure/AWS), and most of those have some managed K8s offering.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#14
post #8
post #3

First coolify[1] and now Tau. More competition the better for users. From the quick look it seems like coolify is more fully featured? [1]: https://coolify.io/

Before Coolify came CapRover and dokku. My toy server (64ram, ryzen 5600G 60tb HDD, 4tb NVMe) is currently running fedora/caprover, though I've been considering just putting truenas scale on it, as it added custom deployments as well...

That's a beast server. What are you using it for?

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#16
post #11

This is really neat! I'm working a message queue in go (drop-in replacement for SQS) and also thinking about autoscaling. I've been playing with raft vs using a central store (ie, postgres) to coordinate. Can you tell me more about IPFS - I've never used it before. How has that been working, and can you tell me what you've observed when you have many nodes which need to coordinate?

IPFS is slow and impractical. The design of the content addresssble system is cool, but having tried approximately annually to run it for production usage since it was released, I can say that it is still firmly in the “research project” category, a decade later.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#17
I've been reading through the docs and skipping through the one recentish YouTube tutorial trying to make sense of what this actually is. While it seems like an impressive thing for what appears to be a one-man-project, the almost complete lack of documentation makes it feel like a bit of a hard no in the current state. There seems to be a history of it being heavily linked to Web3 things that also feels weird.

Some suggestions for this to be able to succeed:

- Documentation, documentation, documentation, the only place where I could that the three supported ways to write a serverless function are with Go, Rust and AssemblyScript is somewhere hidden in a tutorial. It all has to compile to WebAssembly so I guess that's the limiting factor.

- Examples?

- Using git as source of truth for the configuration/state of a system is cool. Please link to sample repos so I can see what a system with a website, some functions that touch DB and files, and the configuration etc looks like.

- How does the database part work? Client SDKs?

- There are lots of protocols with unclear names that are only briefly mentioned here but then seen in random places in configuration: https://tau.how/01-getting-started/01-local-cloud/#protocols

- The Concepts part of the documentation is buzzword soup, it's impossible to derive any meaning from it other than that the author dislikes Kubernetes and probably used some generative AI for the content.

- Roadmap, plans, versioning, plans on how Tau version upgrades should go, ...

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#19

What's with the vilification of kubernetes? 99% of this document ( https://tau.how/99-Misc/kubernetes/01-k8s-cons/ ) boils down to "You have to understand what a pod, deployment, container, etc is" once you remove every line that discusses the cons of managing a cluster yourself, because nobody actually does that except extremely large orgs. All of these problems go away when you utilize a managed offering like DOKS,…

I found it interesting that this was the focus when users of Vercel etc. have probably decided against k8s already. For me, a k8s comparison would make sense if this was a platform for running containers/VMs in a more traditional server model.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#20
post #8

Earlier quoted context omitted.

Before Coolify came CapRover and dokku. My toy server (64ram, ryzen 5600G 60tb HDD, 4tb NVMe) is currently running fedora/caprover, though I've been considering just putting truenas scale on it, as it added custom deployments as well...

That's a beast server. What are you using it for?

It sounds bigger then it is, raid 10 cuts it in half after all (30tb HDD, 2tb NVMe)

It's mostly just for the *arr stack, various self hosted services like vaultwarden, seafile etc and my personal toy projects. I.e. a pwa book reader along with the occasional dev tool I wanna experiment with.

Post reply on HN