[hoechst]

> Similarly, the bare metal solution consisting of nginx with manual Let’s Encrypt cert setup was too much of a hassle.

It's not a hassle. Setup once and then forget about it. It's dead simple, easy and there's a million tutorials on it online.

But it's boring (this is where I'm going to old-man-ramble about things, so better stop reading now). Imo, that's why we have so much bloat, complexity and overkill use of containerization that requires orchestration in software and devops. We don't go the easiest possible route, but the one that seems interesting and most fun.

I totally get playing with new stuff and going totally over board just to host a static html file for a personal project, with the goal to learn something new. But it's not just personal projects, it's whole companies that adopt this kind of approach, not even thinking 2 years ahead, when the "cool new software" you used is now not only not cool and new anymore, but abandoned and unmaintained.

I get that this is just a random "i did a thing" blog post, but this just annoys me :(

[michalwarda]

Sorry to annoy you ^^. I'm not a native speaker and I guess it's my wording in the post. What I meant is "setting it up for every new project I would be working on might be cumbersome".

Honestly I thought only friends and family would read it and I didn't spend enough time polishing the nuances in the writing. I didn't expect it to blow up so much :D.

But going back to the point I fully understand your frustration about the overcomplicated approach. Though for my defense I'm planning on hosting many more apps using this setup. In fact I already am but didn't want to overcomplicate the post.

I left it for part 2. Subscribe RSS for followup xD. I feel like a YouTuber after saying that.