Chris Oliver

That looks correct to me. You may want to run this in your Rails console to verify it is working outside of your action. I can't think of what would cause it to generate the WHERE without a column name there, but it has to be something revolving around your database, associations, or query.

Another thing, have you verified that @location.favorites works correctly? When you hit the create, it makes the record correctly including the user_id?

Hmm, it looks like you've somehow got a bad query. When it says WHERE "favorites"."" there should be something inside those last two empty quotes.

What does your action looks like?

Check out the handful of episodes just before this one to get the bigger picture.

Speaking of Bash! Everyone should update their Bash versions just to be safe. Tons of information here: https://shellshocker.net/

Absolutely! I'd set it up the way you mentioned where categories are higher level than forum threads. Then you could have categories#index as the root of the application and list out those, then forum threads inside. That's basically how http://ubuntuforums.org/ operates.

Thanks! :)

I think it has something to do with the compiler on that version of OSX and/or Ruby. I just found a post on Stack Overflow that might be of help. Here are a bunch of suggestions on how to fix it: http://stackoverflow.com/qu...

That was my bad. I realized I hadn't been making commits while recording but I'll try to do that in the future.

I'll probably do a screencast on Sidekiq (and other background workers) in the future. For now, you might want to check out this post http://chrisdyer.info/2013/...

That sounds like your compiler is too old maybe. I'm not sure the best solution there. What version of your OS are you on and what version of Ruby are you using?

Interesting. I haven't had trouble with that gem before. Did it give you any more text for the error?

Sounds like it's having trouble reading from your Git repo. I'd guess none of that has changed, but you might want to double check it. You can also do the ssh forward agent option if you want to use your local ssh keys to check out the repo in case that is causing the problem. Other than something related to that, I don't know what's wrong.

Done!

Sweeet! I'm going to start using this from now on. Thanks for sharing!

Are you using rbenv, rvm, or something else? That'll help determine what you need and then your ruby version just kind of replaces part of a config line for that.

Make sure your passenger_ruby line in nginx.conf points to the right location. I think if that fails, it probably falls back to whatever is in your PATH which could be an older version like REE.

Oh yeah! Forgot about the bundle console command. I'll be sure to use that more often in the future. Thanks! :)

Mostly just because it's very simple and easy to get up and running. From some recent benchmarks I read, it also performs comparatively to Unicorn and some other solutions out there. Seemed to be a good mix of convenience to learn and performance.

Congrats Anthony!! :) After what seemed like a ton of issues, I'm glad you finally got it all running. I'm sure it will be way quicker next time!

It's like you know what's going through my mind. I'm making a dedicated screencast for div_for. ;-)