nkantar

I’m glad this lead to some learning for you! Some of the comments did that for me, which is great.

Broadly speaking, I explicitly wanted to stay in the Coolify world. Coolify is a self-hostable PaaS platform—though I use the Cloud service, as I mentioned—and I really like the abstraction it provides. I haven’t had to SSH into my server for anything since I set it up—I just add repos through the web UI and things deploy and show up in my browser.

Yes, static sites certainly could—and arguably even should—be done way simpler than this. But I have other things I want to deploy on the same infrastructure, things that aren’t static sites, and for which containers make a whole lot more sense. Simplicity can be “each thing is simple in isolation”, but it can also be “all things are consistent with each other”, and in this case I chose the latter.

If this standardization on this kind of abstraction weren’t a priority, this would indeed be a pretty inefficient way of doing this. In fact, I arrived at my current setup by doing what you suggested—setting up a server without containers, building sites directly on it, and serving them from a single reverse proxy instance—and the amount of automation I found myself writing was a bit tedious. The final nail in the coffin for that approach was realizing I’d have to solve web apps with multiple processes in some other way regardless.

    Location: Los Angeles, CA, USA
    Remote: Yes, exclusively
    Willing to relocate: No
    Technologies: Python, AWS, TypeScript, open to others
    Résumé/CV: https://nkantar.com/resume
    Email: [email protected]
    More: https://nkantar.com/blog/2023/08/hire-me-v202308/

    Location: Los Angeles, CA, USA
    Remote: Yes, exclusively
    Willing to relocate: No
    Technologies: Python, AWS, TypeScript, open to others
    Résumé/CV: https://nkantar.com/resume
    Email: [email protected]
    More: https://nkantar.com/blog/2023/08/hire-me-v202308/

    Location: Los Angeles, CA, USA
    Remote: Yes, exclusively
    Willing to relocate: No
    Technologies: Python, AWS, TypeScript, open to others
    Résumé/CV: https://nkantar.com/resume
    Email: [email protected]
    More: https://nkantar.com/blog/2023/08/hire-me-v202308/

    Location: Los Angeles, CA, USA
    Remote: Yes, exclusively
    Willing to relocate: No
    Technologies: Python, AWS, TypeScript, open to others
    Résumé/CV: https://nkantar.com/resume
    Email: [email protected]
    More: https://nkantar.com/blog/2023/08/hire-me-v202308/

I recently got an OLKB Planck to see if I like it enough to travel with it, as the ErgoDox is a bit hefty for that use case.

If someone asked me what to use for payments on a new project, I don’t think I’d feel comfortable suggesting Stripe, based solely on what I keep reading about the company on HN. That itself also feels a bit weird, especially without a clear alternative.

I myself have used Stripe for a few tiny things over the years, and have never had an issue, but I’d be surprised if I’ve put more than $100 total through the platform.

---

Edit: The comments some have about the legitimacy of the OP’s business may make this particular case a non-issue, to be fair.