docker-rails-example VS Ruby on Rails

I took a 13,000 line Rails 7.0 app and updated it to 7.1. I had to change 1 line of test configuration code to make everything work.

I would say that's a success for having an easy upgrade path. Now the fun part is going back to refactor some of the code to use the new features in 7.1.

If anyone is curious, I updated my Rails / Docker example app to use 7.1 too https://github.com/nickjj/docker-rails-example. Even though Rails 7.1 comes with a Dockerfile, there's still a lot of opinions you can add such as using Docker Compose to have a fully working out of the box experience that works in development and production -- complete with Postgres, Redis, Action Cable, Sidekiq and more.

Even though Rails 7.1 comes with a Dockerfile, there's still a lot of opinions you can add such as using Docker Compose to have a fully working out of the box experience that works in development and production.

If anyone is interested in that, I updated my example Rails app https://github.com/nickjj/docker-rails-example to use Rails 7.1 a few hours after 7.1 dropped.

If you're itching for Docker compatibility I maintain https://github.com/nickjj/docker-rails-example.

- https://github.com/nickjj/docker-rails-example

There's https://github.com/nickjj/docker-rails-example if you're looking for an end to end 1 command solution that works in dev and prod. It pulls together Puma, Sidekiq, Action Cable, Postgres, Redis, esbuild and Tailwind. It's all set up and ready to use Hotwire as well.

If anyone is looking for a more complete guide I put together this a while back: https://nickjanetakis.com/blog/a-guide-for-running-rails-in-...

The post also includes a ~1h hour ad-free YouTube video. It includes running Rails and also Sidekiq, Postgres, Redis, Action Cable and ties in esbuild and Tailwind too. It's all managed by Docker Compose.

The example app is open source at https://github.com/nickjj/docker-rails-example and it's optimized for both development and production. No strings attached.

If you're interested I've created https://github.com/nickjj/docker-rails-example with a base project using Docker Compose, Postgres, Redis, Sidekiq, Tailwind and esbuild.

I create an Up controller https://github.com/nickjj/docker-rails-example/blob/main/app/controllers/up_controller.rb and then have Uptime Robot https://uptimerobot.com/ hit it every few minutes.

[0] is a my favorite demonstration of it.

[0]: https://github.com/rails/rails/commit/b83965785db1eec019edf1...

Here's a real life example: Imagine a Ruby on Rails app on which a team of developers are working. The code is hosted on GitLab and all the work is coordinated using GitLab issues. In other words: For every commit, there's an associated issue and the issue number acts as a sort of primary key for documentation, time reporting and so forth. This convention has a few advantages, most notably the ability to easily learn more about how, when and by whom features were implemented as well as how this implementation came to be.

Ruby on Rails is regarded as one of the best ruby frameworks. It was the primary language in developing big projects such as Twitter and helped the language boost the community. Often referred to as “Rails,” Ruby on Rails is a web development framework with an MVC control structure and currently running its 6.1 version. The 16-year-old language has dramatically influenced the web development structures and managing databases, web pages, and other components on a web application.

In Rails 7.1, a new option _instance_methods is introduced, allowing developers to opt-out of the automatic generation of instance methods for enums. When enum is defined with _instance_methods: false, Rails will no longer generate methods like pending?, processed?, etc.

Rails isn't super opinionated about database writes, its mostly left up to developers to discover that for relational DBs you do not want to be doing a bunch of small writes all at once.

That said it specifically has tools to address this that started appearing a few years ago https://github.com/rails/rails/pull/35077

The way my team handles it is to stick Kafka in between whats generating the records (for us, a bunch of web scraping workers) and and a consumer that pulls off the Kafka queue and runs an insert when its internal buffer reaches around 50k rows.

Rails is also looking to add some more direct background type work with https://github.com/basecamp/solid_queue but this is still very new - most larger Rails shops are going to be running a second system and a gem called Sidekiq that pulls jobs out of Redis.

I'm looking forward to see what extractions from this will land on rails. For example: https://github.com/rails/rails/issues/50454

Here is what strict_loading does (source):

Kamal is a wonderfully simple way to deploy your applications anywhere. It will also be included by default in Rails 8. Kamal is trivial, but I don’t recommend using it on your development machine.

Here's the GitHub milestone I've based this article on — https://github.com/rails/rails/milestone/87