-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
Telegraf
Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.
I would use telegraf (https://github.com/influxdata/telegraf) to gather the metrics you want from your servers. It has built-in functions to get metrics like disk usage, cpu, etc...
From there I would export those metrics to a grafana+influxdb setup. But honestly this is because that's what I'm used to professionally. There might be simpler solutions around.
-
-
It's not an issue anymore. Your main concerns are power and internet stability. Plus, upload speed. The rest can be worked out.
https://www.cloudflare.com/products/tunnel/
https://github.com/cloudflare/cloudflared
https://developers.cloudflare.com/cloudflare-one/connections...
-
And those daemons use constantly 25-30% CPU.https://github.com/k3s-io/k3s/issues/294
-
Maybe try coolify[0] its provides a better than dokku in my personal experience.
0. https://coolify.io/
-
What are you using to manage your schema? Do you use an ORM? Maybe something like PocketBase[0]?
[0]https://pocketbase.io/
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
I looked at pocketbase and other tools, but decided to keep it simple.
Like GP, I'm also using D1 (https://developers.cloudflare.com/d1) which is based on SQLite and still in early Alpha. In combination with KV (https://developers.cloudflare.com/workers/learning/how-kv-wo...) it's trivial to have a great database layer with caching using kysely (https://github.com/aidenwallis/kysely-d1) and trpc (https://trpc.io) you can have typing from DB to front end.
-
I think one of the reasons is that people confuse physical servers with manual administration. As I said, I do not do manual administration. Nothing ever gets configured on any server by hand. All administration is through ansible.
I only have one ansible setup, and it can work both for virtualized servers and physical ones. No difference. The only difference is that virtualized servers need to be set up with terraform first, and physical ones need to be ordered first and their IPs entered into a configuration file (inventory).
Of course, I am also careful to avoid becoming dependent on many other cloud services. For example, I use VpnCloud (https://github.com/dswd/vpncloud) for communication between the servers. As a side benefit, this also gives me the flexibility to switch to any infrastructure provider at any time.
My main point was that while virtualized offerings do have their uses, there is a (huge) gap between a $10/month hobby VPS and a company with exploding-growth B2C business. Most new businesses actually fall into that gap: you do not expect hockey-stick exponential growth in a profitable B2B SaaS. That's where you should question the usual default choice of "use AWS". I care about my COGS and my margins, so I look at this choice very carefully.
-
vps-comparison
A comparison between some VPS providers. It uses Ansible to perform a series of automated benchmark tests over the VPS servers that you specify. It allows the reproducibility of those tests by anyone that wanted to compare these results to their own. All the tests results are available in order to provide independence and transparency.
I dislike Vultr based on their deceptive marketing around the very cheap 2.5 and 3.5$ instances they (used to?) list on their website. Usually those are only available in one or two sites, with no way of checking before creating an account and loading up the minimum amount (10$ when I tried).
They did give me my money back when I asked.
https://github.com/joedicastro/vps-comparison/issues/27
-
Yes, ... and? Those are much more "standardized" than whatever else any team cooks up. (And k8s along with Go is steadily improving, so I don't see this as "let's use WordPress because its the platform that has the most answers on StackOverflow".)
And even if k8s puts on too many legacy-ness, there are upcoming slimmer manifestations of the core ideas. (Eg. https://github.com/aurae-runtime/aurae )
-
It looks like this [1] plugin [2] is supported in jekyll / GitHub pages [3].
So, it seems like adding RSS / Atom feeds on a jekyll or GitHub pages site is pretty straightforward.
1. https://github.com/jekyll/jekyll-feed
2. https://docs.github.com/en/pages/setting-up-a-github-pages-s...
3. https://pages.github.com/versions/
