27 ms·

Rails 8.0 Beta 1: No PaaS Required

26 points by ksec 2y ago

mooreds 2y ago
Hmmm. They suggest running SQLite in production rather than PG or MySQL. As a long time RDBMS fan, I'm not sure how I feel about that.
- tchock23 2y ago
  Years ago we used to tease a guy in our incubator about using SQLite in production. Who knew he was just ahead of the curve…
- PapaPalpatine 2y ago
  They’re not suggesting you use SqLite for your primary database but rather separate databases for caching and job queues. It allows you to drop redis as a dependency.
  - mooreds 2y ago
    Ah, thanks for the clarification.
- strzibny 2y ago
  It's just a default that's being in Rails for a very long time. This let's you start a project quickly. And now the improvements to SQLite is Rails means it's also good to go for a production setup.
nickjj 2y ago
It's good to see more folks getting exposed to this style of hosting. For ~9 years I've been comboing Ansible, Docker Compose and git to deploy web apps to a VPS or more generally any Debian based host. Roughly 10-15 lines of YAML and 1 command to get everything up and running in a production ready way. It really does work, I've deployed about 60 or 70 different apps this way for clients over the years.
- strzibny 2y ago
  Yes and Kamal fixes the small things regarding Compose -- zero downtime deploys, assets bridging, automatic TLS certs, etc. I wrote Kamal Handbook to help people start with Kamal (and currently updating for Kamal 2.0).
  - nickjj 2y ago
    With Ansible you can configure anything such as nginx and certbot. That would handle assets and DNS based wild card certs among other things. If you were feeling adventurous you could also queue up requests with nginx and a little bit of Lua scripting to achieve zero downtime deploys. That's what Basecamp did 11 years ago with: https://github.com/basecamp/intermission https://github.com/basecamp/intermission In practice I find zero downtime deploys with request queuing can get tricky. For example, it's not just your web app that gets deployed. There's also your background worker and action cable process that runs in its own containers and isn't proxied with the same health check as your web container. I haven't used Kamal yet but how does it deal with your action cable process and background worker becoming healthy with v2 of your app while the web app is still serving v1 of your code or vice versa?
    - nightpool 2y ago
      > I haven't used Kamal yet but how does it deal with your action cable process and background worker becoming healthy with v2 of your app while the web app is still serving v1 of your code or vice versa? Isn't this the same problem you'd have deploying your updated code to any number of servers larger than one? There's no way to shift over all the traffic at the exact same time, so all database changes have to be forwards compatible e.g. you can add columns before using them, all code changes have to be cross compatible (e.g. if there are unknown job names or arguments, they get automatically retried)
evjan 2y ago
I’m so excited about all of this. I was about to start creating an Expo mobile app but maybe I’ll just go with Rails 8 and Hotwire Native for now. I know Rails way better and I enjoy it so much.

26 points by ksec 2y ago

Hmmm. They suggest running SQLite in production rather than PG or MySQL. As a long time RDBMS fan, I'm not sure how I feel about that.

tchock23 2y ago
Years ago we used to tease a guy in our incubator about using SQLite in production. Who knew he was just ahead of the curve…
PapaPalpatine 2y ago
They’re not suggesting you use SqLite for your primary database but rather separate databases for caching and job queues. It allows you to drop redis as a dependency.
- mooreds 2y ago
  Ah, thanks for the clarification.
strzibny 2y ago
It's just a default that's being in Rails for a very long time. This let's you start a project quickly. And now the improvements to SQLite is Rails means it's also good to go for a production setup.

nickjj 2y ago

It's good to see more folks getting exposed to this style of hosting. For ~9 years I've been comboing Ansible, Docker Compose and git to deploy web apps to a VPS or more generally any Debian based host. Roughly 10-15 lines of YAML and 1 command to get everything up and running in a production ready way. It really does work, I've deployed about 60 or 70 different apps this way for clients over the years.

strzibny 2y ago
Yes and Kamal fixes the small things regarding Compose -- zero downtime deploys, assets bridging, automatic TLS certs, etc. I wrote Kamal Handbook to help people start with Kamal (and currently updating for Kamal 2.0).
- nickjj 2y ago
  With Ansible you can configure anything such as nginx and certbot. That would handle assets and DNS based wild card certs among other things. If you were feeling adventurous you could also queue up requests with nginx and a little bit of Lua scripting to achieve zero downtime deploys. That's what Basecamp did 11 years ago with: https://github.com/basecamp/intermission https://github.com/basecamp/intermission In practice I find zero downtime deploys with request queuing can get tricky. For example, it's not just your web app that gets deployed. There's also your background worker and action cable process that runs in its own containers and isn't proxied with the same health check as your web container. I haven't used Kamal yet but how does it deal with your action cable process and background worker becoming healthy with v2 of your app while the web app is still serving v1 of your code or vice versa?
  - nightpool 2y ago
    > I haven't used Kamal yet but how does it deal with your action cable process and background worker becoming healthy with v2 of your app while the web app is still serving v1 of your code or vice versa? Isn't this the same problem you'd have deploying your updated code to any number of servers larger than one? There's no way to shift over all the traffic at the exact same time, so all database changes have to be forwards compatible e.g. you can add columns before using them, all code changes have to be cross compatible (e.g. if there are unknown job names or arguments, they get automatically retried)

evjan 2y ago

I’m so excited about all of this. I was about to start creating an Expo mobile app but maybe I’ll just go with Rails 8 and Hotwire Native for now. I know Rails way better and I enjoy it so much.