Chris Oliver

Probably need to find an alternative gem or approach since Draftsman isn't being maintained anymore.

Yep, although it's a bit tricky. You would probably want to do this in ruby, and loop through each notification to see if the next one is the same as the last and then you can build up those into a group to display.

Been thinking about covering this at some point, but haven't gotten to it yet.

Rails will always use fingerprinted files in production, nothing fancy there. You just need to make sure the URL it's looking for matches a file in your current deployment directory on the server.

Does the route the browser is looking for match the filename assets/application-af01d6a4cd32bfcf9b8c41fa5fd1f1501cba6e3953ea8ff518309d0b7a8614c9.css

Those files are served up directly through NGINX, not Rails, so that's where you'd want to be looking.

Update to this series is in the works. :)

Flexbox makes centering things vertically and horizontally really easy. I reference the TailwindCSS docs regularly for that. https://tailwindcss.com/docs/justify-content/#app

Devise hashes passwords and stores them using bcrypt by default. Looks like that may be replaced with clearance_sha1.

That's stored in the encrypted_password column in the database table. If you implement the same hashing algorithm, you can validate them against that column.

Hey Craig!

Check out this episode on Rails credentials. This is what I strongly recommend as all your credentials are easily organized and encrypted. Then in production you only have to set RAILS_MASTER_KEY to decrypt the file. Much easier to manage this way.

https://gorails.com/episodes/rails-5-2-encrypted-credentials

I haven't done direct uploads with Shrine v3 yet, but that's on my todolist.

Exactly. And if you need to rename it or make it more complex, delegate can still let you call reservation.name even though it might delegate through a few objects if you had to add like approvals or some other model in the mix that made things more complex.

Yep, that could be a good use case. I use it frequently for things like that. It's not really any different than saying reservation.customer&.name though with the new Ruby safe operator. It's basically doing that for you in the delegate method, but delegate will let you say reservation.name instead of having to know the customer lives in between.

Hey Christopher,

path helpers like profile_path are not methods on the User model. You can use <%= link_to "Profile", profile_path %> in your view to link to a route that matches that name.

The Rails guides would be a good place to read through how they work: https://guides.rubyonrails.org/routing.html#naming-routes

This doesn't (and shouldn't) have anything to do with your database. The error makes it look like that because you were trying to call a method on a database object.

Depends on how you're doing authentication. If you're using session cookies, it'll work out of the box. Otherwise you'll need to build your own mechanism that works similarly.

Yup. It's actually going to be faster than querying your database because Redis is all in-memory.

It sounds like they more or less don't want you downloading all their data and creating your own copy. That's their way of enforcing it. There are several good alternatives that might have better licensing.

Great idea!

Sure could. Just install the views, swap the header code with your dropdown, have it navigate after you select with Javascript and that should be good to go.

Only one referrer will get credit, typically that's the last referrer. That's how basically all referral programs work.

It probably wouldn't hurt upgrading to the latest version of mysql2: https://rubygems.org/gems/mysql2

If your app has a .ruby-version file, then it will use the Ruby version in that file for the project.

Actually, think I spotted your error. You're not using ERB for rendering the link.

<a class="nav-link" href="pages_about_path">About</a>

That should be:

<%= link_to "About", pages_about_path, class: "nav-link" %>

pages_about_path is a helper in Rails to generate the string /pages/about for your route. You need to use ERB to make sure it runs that code and outputs href="/pages/about" instead of outputting the raw string of href="pages_about_path".