Top
Best
New

Posted by tradertef 19 hours ago

I run multiple $10K MRR companies on a $20/month tech stack(stevehanov.ca)
812 points | 464 commentspage 5
ZeWaren 10 hours ago|
I run a dozen PHP (Laravel) / MySQL / Redis apps on a single server which cost 45€ per month.

Applications each have their own FreeBSD jails, so they're isolated.

ZFS incremental replication on top of regular app backups provide a quick recovery process should the hardware of that machine fail.

Moving those apps to the cloud would cost orders of magnitude more, for benefits I don't need.

BobBagwill 13 hours ago||
Modern tech stacks always remind me of this cartoon:

https://www.toontales.net/short/lumber-jerks/

Acme Toothpicks

ewams 4 hours ago||
How do you handle billing / payment processing?
cagz 17 hours ago||
Nice tech read, but without information about which companies, doing what, just feels way too click-baity.
xxxxxxxx 14 hours ago||
This is similar to what I do. Linode, Debian, Go, HTMX, SQLite (with modernc.org/SQLite so I have no CGO dependency) and Caddy. If I have apps that need a lot of storage, I just add an S3 bucket.
hackingonempty 18 hours ago||
> If you need a little breathing room, just use a swapfile.

You should always use a swap file/partition, even if you don't want any swapping. That's because there are always cold pages and if you have no swap space that memory cannot be used for apps or buffers, it's just wasted.

berkes 17 hours ago||
I always thought I had to add a swap file to avoid crashing with OOM. I wasn't aware of the cold pages overhead.

Sometimes that crashing is what I want: a dedicated server running one (micro)service in a system that'll restart new servers on such crashes (e.g. Kubernetes-alike). I'd rather have it crash immediately rather than chugging along in degraded state.

But on a shared setup like OP shows, or the old LAMP-on-a-vps, i'd prefer the system to start swapping and have a chance to recover. IME it quite often does. Will take a few minutes (of near downtime) but will avoid data corruption or crash-loops much easier.

Basically, letting Linux handle recovery vs letting a monitoring system handle recovery

mixmastamyk 4 hours ago||
People seem to be using zram today. Maybe not on servers.
dwa3592 10 hours ago||
>>The optimal strategy is simple: write brutally detailed prompts with strict success criteria (which is best practice anyway), tell the agent to "keep going until all errors are fixed," hit enter, and go make a coffee while Satya Nadella subsidizes your compute costs.

100% agreed.

pelorat 16 hours ago||
This is how every website used to be run before everyone fell four the cloud trap.
pdimitar 14 hours ago|
Love your username and how it relates to your comment -- and the topic at hand.
cmiles8 13 hours ago||
The biggest risk to cloud revenues is that everyone wakes up and realizes they could slash their cloud bills by 60+% quite quickly with just some minimal leaning.
pdimitar 14 hours ago|
I do appreciate the technical simplicity argument and I'm always advocating for it. And the few neat tricks i.e. Copilot.

That being said, I'd much rather read a few ideas for good recurring passive income. Instead, the author kind of flexes on that, then says "I get refused VC money because they don't see how their money would be useful for me" -- which is one more flex -- and moves on to the technical bits.

It's coming across as bragging to me.

More comments...