Chris Oliver

Under Feature Preview, you can enable "New Code Search and Code View (Beta)"

Check out this: https://github.com/railsadminteam/rails_admin/issues/2990

You should be able ot put this in ~/.irbrc

IRB.conf[:USE_AUTOCOMPLETE] = false

Or you can open the rails console / irb with --noautocomplete

rails console --noautocomplete

irb --noautocomplete

https://gorails.com/deploy/ubuntu/22.04

Renews at the same price. 👍

You should be able to just modify the esbuild command in package.json to run twice.

esbuild app/javascript/application.js --bundle --sourcemap --outdir=app/assets/builds --public-path=assets && esbuild app/javascript/admin.js --bundle --sourcemap --outdir=app/assets/builds --public-path=assets

In no particular order:

• Fly.io
• Render.com
• Hatchbox.io (I built this! 🤓)
• DigitalOcean Apps
• Railway

Hatchbox.io is a bit different because it runs on your server(s) and you only pay for servers. If you deploy 2+ apps on a single server, you save money because most hosts charge per-app fees.

We use Wistia. It's expensive and probably cheaper done with S3 or similar.

Check out the Ruby on Rails for Beginners course and then the Series pages to learn specific Rails topics.

It did now: https://gorails.com/episodes/polymorphic-select-rails-globalid?autoplay=1

Yeah, they actually have to copy the Javascript into the turbo-rails gem periodically to keep it in sync. It's kind of annoying and I'm not sure if it's done automatically with each new release of Turbo.

You'll want to use https://github.com/hotwired/turbo to make the Javascript change. The Rails package just includes a copy of the latest Turbo for convenience so you'd want to fix it in the upstream Turbo JS package.

If you clone the Turbo repo, you can specify the Turbo package in your package.json if you set up an app using jsbundling-rails. That should be easier than trying to modify the gem's turbo.js file.

I'd highly recommend checking out our Rails for Beginners course which you can find here: https://gorails.com/start

Tables are very strict in their layout and so you can't do certain things like make a clickable row. That's why divs are more useful often times.

Also added it to my to-do list of screencasts

It's easier than you might think! You just point the domain to the server and Rails doesn't care what domain it is.

Then you can use like ActsAsTenant to match the domain with an Account. Or Account.find_by(domain: request.domain) if you want to do it from scratch

Hey Andrew,

Most of these things change very rarely, so they're not actually outdated.

If you're deciding between Rails and Laravel, try them both! Ruby and PHP are very different languages so you might enjoy one over the other. Both web frameworks offer pretty similar options at the end of the day.

Thanks for sharing this Blake! I just chain mine together so I don't have the additional dependency. I'll have to do a screencast on multiple output files. 👍

Exactly, there might be some additional things we need that are unique to one service, so having the full auth hash is useful.

Sounds good! It sometimes just takes a little bit of mapping out what you've got vs where you need to be and then the pieces start falling together.