Chris Oliver

That's what I figured. 😉

Thanks man! :)

That's super weird! Just tried it on my Mac and got the same issue. Played about 3 seconds and then stopped. It's definitely the autoplay.

What's funny is that code has worked for a long, long time. I think it's something on Wistia's end. I know they often update the player internals, so it must be something odd the way I'm setting it up. Maybe it's now executing too quickly and causing the player to mess up because it hasn't fully initialized or something.

I'm disabling it temporarily now, so at least we have a fix that will work.

Hey Frank,

Thanks for the heads up! Somebody mentioned playback issues on Slack yesterday. First I had heard of it, but that's obviously a huge priority to fix. It's possible Wistia is giving some troubles or something. The free videos are hosted on YouTube so they're different than the paid ones which are on Wistia.

Are you having issues with both or only Wistia? What browser / version and OS are you on? Also if you open up the browser JS console, do you see any JS errors on the page?

Curious to hear what you find out. I didn't have any issues personally, but only tested rbenv. Now my Windows 10 install is borked and I haven't had time to fix it so it boots again.

Not entirely sure on that one. Have you guys tried using rbenv instead?

1. Usually I would say never to modify those and instead override them with your own styles that are included afterwards. It's a bit more work to do the overrides, but if/when they release a new version of the theme, you can replace the vendor files and all your overrides will still exist. It's really, really hard to keep track of what you changed if you modify the original theme. Of course, things like image links in the CSS probably need to be changed regardless, so you may have to make some modifications to the original theme no matter what. The fewer changes you can make, the better.

2. The <%= yield %> is there so that the layout knows where the main page content from the views should get inserted. You can also use it for some other things, but yield without any parameters tells your template where you want the main page content to be.

3. If they're CSS files you can do the same thing as I did, except you can't use variables. Both LESS and SCSS compile down to regular CSS so you can use them together, just in separate files. I believe you can also change the theme's filenames to .scss if you wanted because CSS is all valid inside SCSS. Kinda confusing but you should be fine leaving them as .css and doing the imports like I showed.

Looks like you're on the right track. Step through that and make sure each piece is running like you expect. I would imagine it's something simple in there that's not working right.

Yup, that's basically how I did it too. :)

I just created two form_fors and separated them out. Since both of mine run through Devise, you don't have to do any of the updates to the action because it will just save whatever fields you pass in and it doesn't matter which button was submitted because the logic doesn't change.

You might be able to refactor your action so that it handles things the same way. Basically always try to update the name and profile information. If you didn't receive and field data for it, then no updates are applied. Same for the password. If you didn't pass in the field, it won't attempt to update the password. That would help you remove those two if statements. :)

Usually you will want your mobile app to submit the email/username and password to the sign in endpoint with a JSON format. You can then have the sign in return you JSON for the user, namely the auth_token. That way your mobile app can create its own form, submit the login request, and if it's successful, you can receive JSON for the API key.

Double check that your ~/.bashrc has the rbenv lines in it. This happens when bash doesn't properly load rbenv, and that happens because it doesn't add it to the path in your ~/.bashrc.

That will depend on how big your server is and it's configuration. I haven't tested any websocket stuff at scale, but I've seen some performance tests for 10,000 users before. It starts to slow down at a point, and they were using simulated things, so never real world data. Your mileage will probably vary quite heavily if you start going past a couple thousand users.

Let's pretend I planned that. 😉

Absolutely. Check this out: https://gorails.com/episode...

I have my redis server always running on my laptop on the default port so it is always ready to go. Homebrew comes with instructions on how to start it when you login. If you follow those it will set it up the same way I have.

Perfect. Thanks for sharing that Bob! :)

Yep. You can implement the subscription webhook that gets triggered on delete (or cancel, don't remember the exact name) and just have it remove it from the user on your end. You'd build it same as the other one, but just remove the subscription ID from the user.

I'm hoping to get into React soon!

One of the main things with caching for it will be that you only really need to focus on caching your JSON that the React code will load since it generates the HTML. You won't get performance benefits from caching HTML like you would with Rails, so you can do it on the JSON instead.

That would be https://aws.amazon.com/elastictranscoder/ There's also https://zencoder.com/en/

Hey Giorgos,

This is absolutely a complicated thing to do unfortunately. There are a lot of things that just aren't well defined yet for recording audio and video.

1. The best place is probably going to be storing your videos on Amazon S3. You can use their transcoding service to make the videos web compatible and take screenshots and send the results back to S3. You can also put up a Cloudfront CDN in front of that so downloading the videos will be faster. You'll also only pay for what you use, so the more downloads you get, the more you'll pay. Helps to have your costs scale accordingly.

2. You can check out some things like this which will allow you to record the webcam and audio in HTML5. https://addpipe.com/blog/mediarecorder-api/

And there's webcamjs which will be useful I'm sure: https://github.com/jhuckaby/webcamjs

I don't know too much about all this but I'm likely going to be diving into a video project deeply sometime soon so maybe I'll know more in a month or two.