Chris Oliver

I believe Postgres preserves insertion order for simple queries, but when you start getting into more complex where conditions and things it will not. Always good to specify an order if you're expecting a certain order in your results. 👍

Not quite yet. For example, I'm trying to build a Trello clone with Stimulus Reflex right now. Everything works great, however when I try to broadcast updates to other browsers, that's going to blow away any editing the other users might be doing. I'm talking with Nate tomorrow about it so hopefully I will have some answers. For right now, it seems real easy if you're just wanting realtime updates for a single user.

Exactly. Serialize the whole form and send it over to SR. Stimulus controller would make that the easiest, naturally.

The optimism gem is already built to do that btw. https://github.com/leastbad/optimism

Nah, you'd just add those queues to Sidekiq, delayed job, etc.

Make sure your background workers are processing the action_mailbox_routing and action_mailbox_incineration queues.

Hey Ted,

Honestly, I'd just recommend using stimulus-flatpickr as it will do the setup/teardown automatically for you when Stimulus connects. Makes for very simple Turbolinks compatibility.

As for just fixing the flatpickr instance when it renders cache, you're exactly right. That's what you'd want. It will make sure it tears down before Turbolinks caches the HTML and that's exactly what you need.

Stimulus makes it a piece of cake, so I've started moving to creating Stimulus components that do the setup/teardown rather than listening to turbolinks events. It works with Turbolinks, with the additional benefit that it will also setup/teardown whenever you dynamically add HTML to the page from an AJAX request or websocket which is really nice.

Probably need https://stackoverflow.com/a/51110844/277994

And you can definitely configure it to only create the websocket connection on the page you want like what you're describing. Just gotta write your JS to detect the page and connect when it's the correct one.

Websockets are just designed to be a persistent connection. As you're browsing the site the connection can stay idle until you need it. GitHub, for example, will leave the websocket connection open as you browse but only subscribe to receive events when you view or leave a Pull Request or Issue.

ActionCable should be on every page and always connected. You don't want to disconnect and reconnect constantly.

You simply want to ignore updates if they aren't relevant to the page you're looking at.

Check out the Actionmailer guides: https://guides.rubyonrails.org/action_mailer_basics.html

If you had a LeadMailer that sent a new_lead email, it would be:

LeadMailer.with(lead: @lead).new_lead.deliver_later

👍 The course will definitely help explain how all the payments stuff works better. Especially now that it's crazy complicated with SCA.

I should make a quick tutorial on one-time payments with Jumpstart Pro, because that's what I'm doing for selling the Jumpstart Pro licenses after all. I'll try and squeeze a screencast in today if I can.

@bradley Yeah, I redid the whole thing but turned it into a separate course: https://courses.gorails.com/payments-with-rails-master-class

Covers one-time payments with a shopping cart example and subscription billing, all of it SCA compatible.

(And hilarious accidentally just commented from my laptop, logged into a testing account).

Haha! I don't want to admit, but I do that pretty regularly too switching between my laptop and desktop. 😅

Hey Brian!

Looks like you've got some invalid HTML there. There's a closing tablerow tr tag, but no opening one and you're missing a closing div for the tabs.panel div?

Stimulus Reflex is compatible with AnyCable. 👍

Adam talks about this in one of the Tailwind videos. I'll let him explain it cuz he can do a better job than me. https://twitter.com/adamwathan/status/1245883595396386816

It looks like they're going to be releasing some improvements to Turbolinks and things soon (when they launch Hey.com) that are similar to this. Can't wait to see what they release.

I would definitely recommend uploading with Shrine directly to S3 and then serving the files up through Cloudfront CDN. That way the downloads will be quick as possible which is what you want when streaming.

If you can, you could certainly just have hosting somewhere else like Anchor if they have a way to embed the episodes. It's nice if you can have someone else manage the RSS feed, file storage and serving. We host RemoteRuby on Transistor and I will probably just embed their player if I build a custom site for it at some point.