Chris Oliver

Probably need to do some more work with pgsearch. 👍

Weird, you'd think they'd prompt for the username / password!

RSS is working just fine for me. What do you mean it no longer works?

Hey Nelson,

You should be able to listen to the change event on the file field. That fires anytime the input value changes. Use that to fire off the form submit.

Hey Rick,

Absolutely. If you can imagine it, you can build it. For following hashtags, you'd want to create a model for the Hashtag and then very similar to following users, you'd create a model to join the two records. I'd call it UserHashtag or something and just belongs_to :user and belongs_to :hashtag

Oh simply because that's what TailwindUI was using and I wanted to ship the site instead of porting their examples to Stimulus. I forgot I still need to convert those!

Typically I just create a model called Group and a model called GroupUser that keeps track of which user is in which groups.

No gems for it that I know of since everyone tends to implement it differently.

Pundit is great for handling permissions and Devise is great for authentication pieces. The Group and GroupUser models will let you connect the two.

Hey Camilla,

I almost always use the Devise wiki page to not require the current password to update their account. That would make it so the user wouldn't have to know their password to update.

And this would make for a fantastic screencast... 😎

One trick I like is using signed GlobalIDs. This way you can reference any model. Your form could list all the guests and employees and submit their SGID over to the booking to be transformed to the proper record.

They must be signed global IDs to prevent tampering though.

Definitely looks like a good solution if you can't use Javascript. No Javascript is sure going to cause a lot of frustrations for every other feature.

Generally for staging, you can just deploy the app to a single server to save money compared to the production fully load balanced cluster.

You should loop through @user.user_items.includes(:item) instead so you can access the quantity without an extra query. The includes will load the items records efficiently so you aren't doing any N+1 queries.

has_and_belongs_to_many does not allow you to access the join table, and therefore it's very rarely used.

Instead, you just want to define a has_many :through association.

class User
  has_many :user_items
  has_many :items, through: :user_items
end

class UserItem
  belongs_to :user
  belongs_to :item
end

class Item
  has_many :user_items
  has_many :users, through: :user_items
end

This way you can interact with the join table and add things like quantity.

Turbolinks is getting a major update now that HEY.com was released and I believe is going to fix this. One of their main improvements was to fix the forms.

There are easily like 100+ OAuth providers so we just have a few of the most popular ones built-in and made it easy for you to add any of the other available ones.

Hah, you beat me to answering it. I was going to say, we made it so that by default any omniauth libraries you add will be automatically handled by the callbacks controller so there's nothing to do unless you want to extend the integration.

Great! Congrats on your first gem. 🎉

There's nothing special you need to do for deploying Webpacker with Capistrano as it's built-in to the Rails assets:precompile step. The only thing you need to do is make sure that NodeJS is installed and in your PATH when deploying.

You don't want to install NVM as the root user. It should be on the deploy user, same as rbenv. Your code always runs and deploys under the deploy user so you want to avoid root.

I wouldn't override it, just add your new method and call it like safe_link_to.

Roughly something like this:

def safe_link_to(name = nil, options = nil, html_options = nil, &block)
  link_to(name, options, html_options, &block)
end

Then you can add your call to sanitize in there. I think you'd probably wrap options with the sanitize call most likely.