111–120 of 149 posts
Looks compelling, but the docs are extremely vague and full of fluff. The "Why One Binary" is hilariously bad. Almost feels like content to impress managers/recruiters. https://tau.how/02-concepts/03-one-binary/#the-genesis-of-ta...
Starting off with "In the realm of..." instantly gave it away
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...
I found CapRover and dokku to have some limitations such as lack of a GUI or long setup process. In contrast with Coolify, it Just Worked™. I'll have to check out Tau as well.
Earlier quoted context omitted.
I found CapRover and dokku to have some limitations such as lack of a GUI or long setup process. In contrast with Coolify, it Just Worked™. I'll have to check out Tau as well.
CapRover has a UI to install new apps or configure existing ones.
Isn't the entire point of vercel/netlify/cloudflare is that you *don't* have to self-host? The issue is the price of it, not the actual software. Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected. That 10k bill is roughly $50 dedi from hetzner, but the problem with that is that you need a distributed system, for that you need something more advanced that tau, let's say kubernetes…
Earlier quoted context omitted.
Do you mean it’s missing features or that it requires lots of maintenance and handholding? I’m evaluating some of the options for toy projects so I’m curious to read people’s experiences.
IMO it adds a bunch of complexity (as these types of catch all frontend solutions usually do) to a problem that can be easily solved by becoming proficient in using Docker/Podman and spending a little bit of time reading the documentation for the services you want to run. Its a cool idea but uncessary IMO. There are also a ton of people that like it and I'm just one opinion. I reccomend you try it but I also think yo…
And for that it worked remarkably well
Earlier quoted context omitted.
6x6GB + 2x12gb
Then you have 24 TB with RAID10, not 30 TB. I guess that's why he was wondering.
The 6x6TB were previouly in a Synology NAS (roughly 8yrs old now) and I was planning to slowly migrate everything over to 12TB disk's as things start failing
Isn't the entire point of vercel/netlify/cloudflare is that you *don't* have to self-host? The issue is the price of it, not the actual software. Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected. That 10k bill is roughly $50 dedi from hetzner, but the problem with that is that you need a distributed system, for that you need something more advanced that tau, let's say kubernetes…
Geo distribution is something that everyone that can, should avoid. It just scales up the problems.
Earlier quoted context omitted.
The management when something goes wrong (take this from experience) is very time consuming, especially if you lack experience and/or dedicated staff. Git history deployments is a simple k8s controller, pretty sure there's a helm chart for that. Autoscaling is what I mean by kubernetes so yes totally agree. Coolify seems pretty neat. Still has the overhead of management when dealing with clustering and multi-site.
Some good points to discuss here. Firstly the git history managed via a controller / helm chart. That’s sufficiently complex. The mindset of k8s/cloudnative doesn’t translate easily from the pet vps control server which comes with its own disk and persistence. So conceptually a management layer like cooling is objectively easier. But that’s a nit really. I think the idea of management being time consuming is more int…
I definitely do have the experience when it comes to geo distribution and multi-site deployments, but it's something that took me 2 years to build up to and I genuinely think that it's also not something most people have patience for or freedom for. I am lucky that I can afford to experiment with all of these things on my personal cluster and then turn that into something I deploy when dealing with customers.