docker-rails-example VS vite_ruby

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.

With the recent release of Bun and its newfound support for Vite, coupled with Ruby on Rails 7.1 incorporating native support for Bun, developers can now enhance their web development workflow significantly. Here is the effortless process of enabling Bun for Vite Ruby, ultimately streamlining your front-end builds.

Vite, in particular, ViteRuby is a solid option. It sits between ESBuild and Webpacker, and if you're looking at Webpacker, Vite may actually be a better option for you. It is a very solid option, and I've enjoyed using Vite personally.

Yep. vite_rails (website/GitHub) is the way to go.

Use vite with https://vite-ruby.netlify.app/ if you don’t go the inertia route.

--skip-javascript is necessary for avoiding conflicts on the next steps. In case of bootstrap/foundation-sites the asset pipeline is helpful so --skip-asset-pipeline is not applied.

Vite Ruby is an umbrella project with libraries that will allow you to easily integrate Vite at your favourite Ruby framework, such as Rails or Hanami, or a plain Rack app. If you are tired of waiting for webpack to compile, this project might be for you. ​ Vite.js in Ruby ## Why Vite? 🤔 Vite does not bundle your code during development, which means the dev server is extremely fast to start, and your changes will be updated instantly thanks to HMR. This is great when adjusting styles, or tweaking behavior in JS. In production, Vite bundles your code with tree-shaking, lazy-loading, and common chunk splitting out of the box, to achieve optimal loading performance. ## Why Vite in Ruby? 🤔 Vite is great on its own, but configuring it correctly to work for a Ruby app structure requires knowledge of its internals. By following existing Rails and Rack conventions, and adding a few of its own, it becomes possible for ⠀everyone to leverage Vite and its wonderful features! If you are curious about the difference, check this Jumpstart Rails template.

Vite Rails Docs

It something that basically doesn't work properly since the birth of Rails, 15 years ago. For beginners, this is a big disappointment. You have to tweak Guard-livereload (tricky and not always working, as you mentionned), or try things like browserSync (also tricky, also not always working...) My advice so far : keep Sprockets, in order to have a nice integration with older gems. And completly remove the current js-bundling + importmaps. Instead, replace with the gem 'vite_rails' (repo here : https://github.com/ElMassimo/vite_ruby).