Chris Oliver

Yep, you'll just have to use the Custom VPS option and have your server created on Hetzner first.

And here you go: https://github.com/excid3/jumpstart

Hey Allison,

It's still a work in progress, but let me upload it and share it for you. I know several other people have asked and I just never really felt it was ready enough to share, but then anyone can help fix bugs. :)

I think it is:

<% if devise_controller? %>

Are each of these SSL certs in a separate file?

Are you restarting nginx with `nginx restart` or `nginx reload`?

I've never dealt with near that many SSL certs so that's certainly a new problem to me. I did find this blog which talks about handling 1022 sites and SSL certs with server configs: https://jeremyfelt.com/2016/01/16/managing-ssl-certificates-and-https-configuration-at-scale/ Seems like it has a couple tips that might help.

As far as Heroku goes, I had to add the nodejs buildpack to my Rails app so it would properly compile Webpacker with Ruby. You basically end up with both the Ruby and Node buildpacks and that gives all the Ruby and Node/Yarn versions required to get things going.

It's actually completely custom. I exported my Disqus comments and imported them into the forum. Then extended the forum to have nesting. There are still a few warts here and there because it's doing double duty for comments and the forum, but I'm going to try to clean those up tomorrow.

Make sure you're using rails-ujs and have it included in your asset pipeline. It was introduced in one of the newer versions of Rails to remove jQuery. If you're on an older version of Rails you can either upgrade or change the Rails.ajax to jQuery's version.

Hey Jacob,

Those files are from the new bootsnap gem. They're caching your application's require paths and things in a binary format so your app boots WAY faster. You don't need them stored in your git repo. 

Just thought I would share this in case anyone is interested how Hatchbox.io works. 👍

I literally just rebuilt the comment system (replacing Disqus) so there are some bugs. 🤓

You can think of that approach as similar to binding your events in jQuery. I worked on a nice little wrapper for that which I need to release. And once I get a chance to check out this other approach, I'll let you know. Might be a better way to structure things. 

Hey Justin,

You can do multiple components on a page by creating multiple Vue apps. You'd basically just mount your different Vue apps to the appropriate tag, if you find them on the page. You won't necessarily have them on every page, so you'll need to conditionally check to set them up. 

This is what I do with the Vue-Turbolinks integration. You can see an example here that checks each turbolinks pageview for the components and then sets up the vue app. https://github.com/excid3/vue-turbolinks#running-vue-only-on-specific-pages

You'd just do the same thing basically. 

I also noticed that Laravel seems to have an interesting way of doing things that is using the whole server sided rendered HTML as the main component. It seems like it might be a really useful way of doing an even nicer middle ground.

Thanks Stephen! Good catch on the YouTube URL.