dbackeus

5 ms·

1.
by dbackeus 2y ago
In theory, from a performance point of view, we could easily run our main Rails monolith on a single server. One does not chose single server deployments when reaching for four nines of uptime though. We also run a lot of ancillary applicat
2.
by dbackeus 2y ago
Because it's a fully featured public relations platform, not just a "newsdesk" (though that's what it started as some 20 years ago). We have a main monolithic application at the core. But there are plenty of ancillary ap
3.
by dbackeus 2y ago
I suppose it is. But no actual users of the platform has had any complaints about it.
4.
by dbackeus 2y ago
Not from our point of view since Cloudflare's DDOS production and CDN is a crucial part of our architecture. That said, switching out cloudflared for a more traditional ingress like nginx etc would be straight forward. No parts of the
5.
by dbackeus 2y ago
> Who are your target audience? Anyone looking for a PaaS alternative matching or exceeding the UX of Heroku. The "is it for you" section of our Introduction may give a better idea: https://reclaim-the-stack.com&#x2F
6.
by dbackeus 2y ago
It's all in one app and the app has a ton of users. Anyone running the app can join any server with a click of a button. There are no separate accounts required to join different communities. So communities being separate "spaces&
7.
by dbackeus 2y ago
This documentation only pertains to the Cloudflared ingress servers, which can handle orders of magnitude more traffic than we actually get. So we have not had any need to look into load balancing of this part of the infrastructure. Our act
8.
by dbackeus 2y ago
Feel free to join the RtS discord if you want to bounce ideas for your upcoming infra
9.
by dbackeus 2y ago
Main difference is that Dokku is a simple single server platform, geared mostly toward hobby projects. Reclaim the Stack provides a fully highly available multi node platform to host large scale SaaS applications aiming for four nines of up
10.
by dbackeus 2y ago
Coolify does look nice. But I don't believe it supports HA deployments of Postgres with automated failover / 0 downtime upgrades etc? Do they even have built in backup support? (a doc exists but appears empty: https://c
11.
by dbackeus 2y ago
(Reclaim the Stack creator here) We don't do autoscaling. The main reason for Kubernetes for us was automation of monitoring / logs / alerting and highly available database deployments. 37signals has a dedicated operations te
12.
by dbackeus 2y ago
We've since migrated more stuff. We're currently saving more than $400k/year.
13.
by dbackeus 2y ago
K8s works with both local storage and networked storage. But the two are vastly different from an operations point of view. With networked storage you get fully decoupled compute / storage which allows Kubernetes to reschedule pods arb
14.
by dbackeus 2y ago
> Assuming average salary of 140k/year Is that what developers at your company cost? Just curious. In Sweden the average devops salary is around 60k. > you are dedicating 2 resources 3 times a month and this is already costing yo
15.
by dbackeus 2y ago
The get-started repo is the starting point for installing the platform. Since the platform is gitops based, you'll fork this repo as described in: https://reclaim-the-stack.com/docs/kubernetes-platform/insta..
16.
by dbackeus 2y ago
Creator of Reclaim the Stack here. The idea that we're implying you need 2 full time engineers is a misunderstanding. We just mean to say that you'll want at least 2 developers to spend enough time digging in to Kubernetes etc to
17.
by dbackeus 2y ago
Original creator and maintainer of Reclaim the Stack here. > you also removed monitoring of the platform No we did not: Monitoring: https://reclaim-the-stack.com/docs/platform-components/monit... Log aggregati