|
|
|
|
|
|
by vsgherzi
21 days ago
|
|
|
Yknow unfortunately I just don't think we're going to see eye to eye on this one. I really don't mind that small amount work and I enjoy owning and operating the entire stack. That dosen't really seem like your cup of tea. The flexibility and learning is more important for me. For example I want to aggregate HN comments and lobste.rs comments and inject that into the HTML before serving. (on the server side so no CORS or other additions) I was considering adding additional metrics to see who is hitting the server and how at the reverse proxy level. This is all stuff I can't really do on a github pages blog. I see what you're saying if you want set and forget that's fine, but like I said above it's a tradeoff. The one server I have just has 80 and 443 open with nginx. I expect it to run indefinitely with little maintenance. |
|
|
I've owned and operated enough stacks e2e both personally and professionally to have gotten over the novelty. The less shit that can go wrong, the better. I sleep better at night not wondering whether any of the constant stream of IPs in my fail2ban log is wielding a yet-to-be-CVE'd zero-day, or finding out that my site has been down for 6 weeks because of some fucking stupid bug in the latest kernel patch or whatever.