jakubgarfield

Joined 16 years ago

Karma

171

Submissions

123

Member since

Aug 4

View on Hacker News

Recent submissions

Comment · 8 months ago

Thank you! I've decided to keep one server per "serious" application. And I have one with a few toy projects that are not critical. Containers would make a lot of sense there. Still containers would make the setup story slightly easier even for this one server (and things like upgrading ruby versions, ...).

Comment · 8 months ago

Good point. I have experience with Rack attack on application level. Would you recommend webserver instead (nginx)? Or even Cloudflare? (I bet they have a solution).

Comment · 8 months ago

You are not wrong. Docker (paired with Kamal in Rails world) would simplify a few bits of the setup. But not all. The reason I haven't switched is:

1. my lack of experience with running docker in production

2. don't fix something if it ain't broken

But I'm planning to revisit it when my current LTS version runs out of support. Also, Kamal defaults change a few core pieces (caddy vs nginx, puma vs passenger) so there's a bit of extra learning curve). Oh and you'd still need to harden the server and keep it up to date.

Comment · 8 months ago

100%. And super easy to scale up to a certain point. Alternatives have it's place though (PaaS is excellent for 100% product focus in limited timeframe, cloud/orchestration when you have scale, Kamal in Rails world is a neat middleground for some extra robustness).

Comment · 8 months ago

I'm using external "send-only" SMTP server (Sendgrid) and Google Workspace as receiving/sending. Email itself is something that I'm not keen on DIYing (though I looked into it and other SMTP alternatives).