Deploying a Ruby web app using Vite Ruby should be quite straightforward.
assets:precompile is a standard for Ruby web apps, and is typically run automatically for you upon deployment if you are using a PaaS such as Heroku, or added in Capistrano scripts.
vite:build will be executed whenever assets:precompile is run, and the resulting assets will be placed inside the
Rake Tasks ⚙️
In Rails, they are installed automatically, so you can simply use them.
In other apps, you can add them manually in your
require 'vite_ruby' ViteRuby.install_tasks
The following rake tasks are available:
Makes a production bundle with Vite using Rollup behind the scenes.
Called automatically whenever assets:precompile is called.
Remove previous Vite builds.
Called automatically whenever assets:clean is called.
Remove the Vite build output directory.
Called automatically whenever assets:clobber is called.
Provide information on Vite Ruby and related libraries.
You can provide
RACK_ENV=production to simulate a production build locally.
Disabling extension of the
During complex migrations, it might be convenient that
vite:build is not run along the
assets:precompile rake task.
You can disable the extension of the
assets:precompile rake task by setting the
VITE_RUBY_SKIP_ASSETS_PRECOMPILE_EXTENSION environment variable to
Compressing Assets 📦
Most CDN and edge service providers will automatically serve compressed assets, which is why Vite does not create compressed copies of each file.
If your hosting service or server setup does not handle compression, you can use a Rollup plugin such as
rollup-plugin-gzip to output gzip and brotli versions of each asset.
Check this discussion for an example setup.
Make sure that the ruby buildpack appears last to ensure the proper defaults are applied.
$ heroku buildpacks === pingcrm-vite Buildpack URLs 1. heroku/nodejs 2. heroku/ruby
If you are starting from scratch, you achieve that by running:
heroku buildpacks:set heroku/ruby heroku buildpacks:add --index 1 heroku/nodejs
When precompiling assets in Heroku, it's better to skip pruning of dev dependencies by setting:
heroku config:set NPM_CONFIG_PRODUCTION=false YARN_PRODUCTION=false