4 ms·
A 301-serving service is an interesting concept for a small service, though. I would probably assemble it from Kore (https://kore.io/ https://kore.io/) and sqli
by juped 6y ago
A 301-serving service is an interesting concept for a small service, though. I would probably assemble it from Kore (https://kore.io/ https://kore.io/) and sqlite, or maybe postgres; the hosting requirements would be pretty low. Maybe I'll do it this afternoon for fun.
Then it would just sit there, despite the fact that it could probably be sold for $15k/mo, because that's not a skill I have. If someone signs up for $15k/mo, it's worth a couple extra afternoons to make it more robust for them.
I'm pretty sure you could have done the same, but selling this stuff is a pretty difficult task!
e: another thing you could do is resell domains through it; you wouldn't be competing with registrar builtins then.
- jermaustin1 6y agoI agree, it was a simple afternoon project on a down day where I didn't have much to do client wise. The original code was only a single nginx config to fix the problem on my sites, when I realized there were others having the issue, I built out an application. If I were redoing it today, I'd probably just have a running caddy server since it does HTTPS as well.
- juped 6y agoStill pretty cool. There's probably a lot of easy stuff like this that could sell.
- Uehreka 6y agoI get it, I get it, enterprises find it easier to pay large amounts than small amounts or whatever and good enterprise salespeople can make that happen because “they’re good”. But jeez, $15k/month?! Yikes.
- juped 6y agoFor the record, I did end up slapping this together with kore/sqlite. 48 src/301.c Could be shorter (I did the error handling lazily over more lines), or the same length with more features. Kore is nice. Anyone want to pay $15k/mo?