Chris Oliver

Yeah, we could cheat and embed the stream. ;) But wouldn't it be sweet to build streaming video ourselves too? :)

That would be killer! This would be better for the chat portion of twitch, but the actual video streaming wouldn't be done using websockets.

Hey Corrado,

This is very related to things I have been planning to do soon. I was thinking about doing one-time email login links and verifying phone numbers is great. What part of this tutorial didn't work for you? I'd love to do this one soon.

For that, basically all you need to do is shovel onto the CSV at the end after you loop through the invoices.

You can just say csv << ["custom", "footer"]

Unfortunately you'll have to paste all the bootstrap styles inline into the email templates. Emails only work with limited CSS.

Ah yep! That would do it! I was going to say, sounds like you've got a reference to "default" in your yaml file.

Yep! The real reason is so that you don't store your production secrets in git for security.

You can definitely do all that, but yeah...it might be a lot for your first venture into JS land! :) You can absolutely add the form in the same page and use the example I linked to for updating the calendar after you create a new event though. Shouldn't be too hard.

Hey Karl!

This is a great question. Voting requires you to determine who did it (the voter, probably a User), what they voted on (the votable object), and which way they voted (up or down) which you could call like "direction" or you could simply store "1" or "-1" as an integer for easy calculating. 1 would represent an upvote and -1 would represent the downvote. You can basically create a model called Vote that keeps track of that information. There's a little more complexity to it when you need to sum up a user's karma based upon all the votes on their submissions, but that can be done by adding up all the votes on their submissions.

If you don't want to build all this from scratch, there's a great little gem called acts_as_votable that you can use: https://github.com/ryanto/acts_as_votable

It will help you create all the models and methods for voting and you basically just have to create links to actions to up and downvote submissions.

I did an episode on "liking posts" that works very similar to this. It's how I did the hearts on the GoRails episodes. https://gorails.com/episodes/liking-posts

It covers most of what you want, but they're basically all considered upvotes. You'd have to add the 1 or -1 code in there to handle downvoting and keep track of which. Then your submission's karma is just the sum of all the upvotes and all the downvotes.

Hope that helps you get started!

The easiest way is actually to use a JS response that sends back the calendar partial and you can just simply replace that part of the page. I made this a while back to show how that's done: https://github.com/excid3/s...

Let me know if that makes sense and accomplish what you're trying to do!

QUESTIONS is a list of all the questions to ask in the various states of the application. When you move to the next state, you can easily lookup the question from the QUESTIONS hash that you need to send out. What happens is that when the user sends a response with their first name, the @reply model gets it's state attribute changed over to "last_nm" and then it knows to ask for the last name. Each time a response is saved, it updates the state to the next one. I made a couple episodes on state machines and the state machine that can help you wrap your head around this part:

https://gorails.com/episode...
https://gorails.com/episode...

That's a great question Brian. I think that what I was experiencing was that the jQuery code I wrote never gets re-executed when the page changes via Turbolinks. Usually jquery-turbolinks fixes that by hijacking the page change event and that automatically fixes it. You might double check to make sure that jquery-turbolinks is being included in your application.js file properly. That's about the only thing that I can think of off the top of my head.

Thanks Nick! :)

Sure! Send it my way!

I'm a huge fan of React and think it's been particularly well thought out. Facebook has spent an enormous amount of time engineering things and came up with a pretty novel approach. One of the clues (for me) that I should avoid Ember was how quickly they were rolling in features and ideas from everywhere else. React's server side rendering is wonderful but Ember chose not to address it for a long time until React came out. They just end up copying a lot of things and I'm afraid that's going to lead towards bloat more than a fantastic framework.

RubyMotion is also a great option. I don't know too much about it, but I believe that this is what Basecamp uses for their iOS mobile app. They have their custom JS framework that works with Turbolinks so I'm sure this made a lot of sense to them.

I think you're pretty solid either way you go. The React community is about a thousand times larger than Turbolinks + RubyMotion I feel like which means you might get a lot more support along the way. This is just a hugely biased opinion from me though, so take it with a grain of salt. ;)

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). ;)