There should be an error further up when you try to start the app.  Also, how are y'all starting the app? You should be using 

bin/dev

as this will start the rails, css and js services.

Have a look at AWS App Runner. It is pretty cool what they're doing with this and since it is just using docker images, there is little infrastructure for you to manage on the application side of things. You'd still need the database server and any other services, but the application bit is taken care of. 

I also found that Beanstalk is pretty simple to maintain once you get things up and running. It's initial configuration of things was rather difficult, but a lot of this changed with Amazon Linux 2.

Check out the two most recent episodes around AWS for two paths that I'd recommend.

https://www.driftingruby.com/episodes?query%5Bname%5D=aws

I'll cover one with Digital Ocean and their App Platform. I would probably avoid their normal ocean droplets since scaling those servers isn't very realistic as an application goes. Their App Platform has better support for scaling and server provisioning.

I created a new rails application with

rails new testapp --javascript esbuild --css bootstrap

Then ran 

rails action_text:install

I created a resource and attached an attribute with the has_rich_text and it seems to be working properly. Make sure that you have yarn installed on your system. In my case, it imported the actiontext.css in the application.bootstrap.scss

@import 'actiontext.css';

And it rendered properly.

Yes. I probably wouldn’t do that on a real app. If I were, I would limit the pagination to something like 5 and also make sure that the responses were very fast. If I start seeing memory issues or scaling problems in the actioncable side, I would rethink this to either do a refresh interval or switch to any cable.