Chris Oliver

Strange. What does thr javascript console say for errors?

Try using the search icon in the navbar.

This would be a good one for the Rails github issue tracker.

I would bet they don't have that by default, but could probably be done by pasting the Rails source into your app, editing the toolbar for Trix, and then including your modified copy instead of the Rails JS for it.

ActionCable works great for this. Once the background job retrieves the data, you can have it send an updated partial over to the user and replace it on the page. I do this for server and app status updates on Hatchbox. Works great.

Awesome! I've got a long weekend out of town, but when I get back I can probably crank on a few episodes that start from the very basics.

I don't think there's any way to do this in the database with the current setup, so what you're doing is probably what I would do.

You could cache the results of the report and re-calculate them every day or week on a regular basis so you don't have to run this expensive calculation all the time.

I'd probably stick with what you've got.

haha! ive done that many times myself. Coding while tired doesnt work out very well.

Maybe a cool feature to add is checkboxes so you can see which steps youve completed!

You can run that code in the console by running the same code as you would in your app. response = Documents::CreateSession.new.start

The response will be the return value of start as it currently is setup.

The "Installing Ruby" step covers installing git, node, yarn, build essentials and the libssl, libreadline and zlib libraries. Sounds like you might have missed those steps.

Most of us prefer the Pundit gem for that. There's an episode on it as well. 👍

Not quite yet! I'm still working on it but keep getting distracted with other things. I'm hoping next week I can dedicated a lot of time to getting it all figured out and then re-record the course after that.

Moving a database isn't so easy. You typically incur downtime, or you have to setup streaming replicas and things that are complicated.

1. You can either pay for DigitalOcean's managed load balancer, or let Hatchbox create one. You probably just need a $5/mo server for that.
2. If you use their managed database, it's not a server you'll have in Hatchbox, so it doesn't count. They also have managed Redis now too that you could use if you wanted. Having managed databases that you don't have to worry about is really really nice. Hatchbox doesn't do managed yet (and we might never need to if these services keep popping up), so those are worth looking into.
3. The number is however many servers Hatchbox creates and runs for you.
4. Depends on how many background jobs you plan on running, but yes, seems good.

Not currently, but I'm actually working on one! What's your knowledge about web development so far? Have you learned anything else or are you starting completely new with Rails?

Check out this series: https://gorails.com/series/embeddable-javascript-widgets-with-rails

Looks like I accidentally changed the naming scheme for that episode. 🧐

Pretty much has to be an external service, since you want it running independently of your app. And, so you don't have to also monitor and run your own uptime monitoring, most people just pay for something.

I like and recommend HoneyBadger.io will do uptime checks, check-ins, and error monitoring all-in-one. Nice to have those features together in the same app rather than paying for multiple things. They have a free solo-dev option that comes in handy.

You've also got tools like Pingdom that will do performance / uptime. Lots of other options out there too.

Since it says your comments table has no post_id column, you should check your migrations and make sure you didn't forget to add the column. :)

Just to re-iterate here, we had a brief discussion of this on Twitter.

For GoRails, I simply removed links to the old plans when pricing changed. I created the new plans in Stripe and linked to them on the pricing page in the app. Existing customers stayed on the old plans and new customers could only subscribe to the new plans.

Everyone gets grandfathered in that way, and any special cases where I might need to set someone up on the old grandfathered plan can be done manually in the backend.

The payments library we're using for Jumpstart Pro, Pay, doesn't handle marketplaces right now. You'd need to implement Stripe Connect yourself instead.

At some point in the future, we'd like to support that, but we're upgrading everything to be SCA compatible first. Then we will probably look into marketplaces, but since we support both Stripe and Braintree, that's a bit harder to make them both work similarly, especially for marketplaces.