It will probably work with UJS, but I would probably move things over to a fetch so that it will work longer term if you move fully to hotwire.

I haven't tried it out with two actiontexts, there may be somethings that need to change with the controller to handle it properly with two action texts on the same view.

What issues are you experiencing with Sidekiq?  ☒ ? What does your infrastructure look like? I actually cheated a bit with my instance and actually run Sidekiq on the web servers. It's not best practices, but it works. If you were to separate out the sidekiq from the web servers, you'd create a separate application within your environment.

 ☒ It should work with Rails 6.x. However, you likely had turbolinks in that application and you would have to convert it over to Turbo (hotwire) to work properly.

As far as the modal stuff goes. This can get a bit trickier. Likely, I would have an empty turbo frame tag in the layouts for the modal. When you click the Edit Comment button, it would make a request back to the rails application for that comments#edit. From there you would have a turbo_stream response and an associated edit.turbo_stream.erb file which would then replace the empty turbo frame tag in the layouts with a partial which had that turbo frame tag and the modal information. You would then have, within that partial, a stimulus controller something to launch the modal when the controller connects. Hope this makes sense.

You could render the modals inline with the content, but the main issue there is that you're spending CPU cycles and bandwidth in creating these modals that might never be triggered. This does sound episode worthy as it can be a complicated feature. 

 ☒ Unfortunately, the Deployment Alternatives episode isn't looking too good right now. App Platform has a major issue with using an old heroku/ruby buildpack version. This is a problem because it will not allow for the deployment of a yarn-based Ruby on Rails application without webpacker. Essentially, you have to use webpacker and not jsbundling-rails or cssbundling-rails. I'm in talks with the Digital Ocean team to see if they can get this resolved, but as such, I will likely have to postpone this episode until they update their platform.