Chris Oliver

Interesting. I'd love to cover that, although I have no idea what it takes to setup an ADFS server in order to try all this out. It does look like it's pretty tricky to accomplish.

Do you have any idea if it's easy to setup an ADFS server?

Hey Chris!

As long as you're using HTML5 for the video streaming, you should see this underneath: http://cl.ly/d82h The paid videos are hosted on Wistia, so those controls show up for them. The free videos are hosted on Youtube, and you can click the gear in those videos to speed them up.

You got it! :) I appreciate that a lot. I've been trying to make sure it all stays up-to-date as much as possible.

Lemme know if you hit any snags!

You'll love this, it's almost too simple.

For your new app, you can basically copy the Capistrano configs from the old one and change the app name in all the places. You'll need to add another server block to your Nginx config, restart Nginx, and create a new database for this app. That's it. Just deploy like you did before, and create the database.yml file on the server to point to the new database and you're off to the races.

Changing the domain name in the nginx config and pointing a second domain to the same server is all you need to do in order to have Nginx serve up two sites from the same machine.

You can basically just follow those same steps from the guide, but skip the installation parts and go straight to the nginx config, database, and capistrano pieces.

Always glad to help! Let me know how it goes (and how lunch is). ;)

The Gibbon gem should let you do this. You can add someone to the list when they sign up. This is what I do with GoRails on registrations so that I can send the announcement emails out with Mailchimp. That *should* do the trick for you there.

Great points! I'll get on this. :)

Hey Aaron!

It might make the most sense to have a post_type field that's video, blog, or poll. You could then dynamically add new types easily and have each of these render out different partials based upon the type. That's really the simplest way of doing it. You'll still query one model which keeps things all together, but the rendering will show the different types of content.

You can also take this a step further with what's called Single Table Inheritance or STI. You could create Blog, Video, and Poll models that inherit from Post and then you can organize your code out nicely inside these various models for the code that's specific to each type.

More reading for you on STI: http://eewang.github.io/blog/2013/03/12/how-and-when-to-use-single-table-inheritance-in-rails/

Yeah it was not a very good series. I didn't show the whole thing and just emphasized certain parts. Are you interested in seeing the whole thing? I might do a revised series on it or something similar.

This doesn't make sense for a site that's globally locked down. That's why it's designed in the way that it is.

If you're locking down everything, the Devise before_action :authenticate_user! can take care of that for you. You can also put that in ApplicationController to have it apply to every single request.

Hey Alejandro,

2 things:

1. You accidentally pasted your password into this (I edited it out), but you'll want to go change that now.

2. It sounds like your SSH key is not added to Github. It's connected to the server and now needs to ask Github for your code so that it can put it on there. That step has failed and so you'll want to make sure that your ssh key is added to your user account on Github.

Thanks for the kind words! :D

I've definitely been planning on adding that. Here's a question for you. Which makes more sense? Having it automatically marked as "played" like Youtube does or having a button for you to mark it as watched? My first impression would be is the automatic one seems like a better idea, but I'd love to hear your thoughts (and anyone else's) on this!

Also I need to get emoji support in the forum ;-)

I haven't done an episode on it, but for now, check out this tutorial. It should do the trick for you! http://sourcey.com/rails-4-...

That gem seems super interesting. Haven't seen it before. Thanks for sharing!

I almost always recommend making sure you use the same database in development as you use in production. That way you don't get unexpected results when deploying.

Ah! That would do it! :)

Sounds like you don't have an SSH key on your machine. You might need to generate a new one or install an old one if you have one you created previously.

Yo! So I think having accepts_nested_attributes_for is really the main thing for making this work. The only other thing you really need is to make sure that your strong_params in the controller accepts those attributes.

What it will do is create or update the Company with its own attributes and then accepts_nested_attributes_for will automatically create the nested models for you (the Users) and it will also associate them too.

Probably the main thing to watch out for is that you need to also make sure the nested models are validated. Devise is going to require a password for the Users (by default) so you'll possibly need to set some default passwords for those users.

Are you having trouble making this work? Also the cocoon gem is great for creating those nested forms for the nested models. https://github.com/nathanvda/cocoon

That's my goal!

I keep it updated as much as I can! :)

I haven't seen or used devise_group before! Thanks for sharing this. Looks super useful.