rbenv install
bundle install
bundle exec rake db:create
bundle exec rake db:migrate
bundle exec rake db:seed
I'm getting the vibe that actioncable/websockets are not going to play nice with Turbo(links): https://stackoverflow.com/questions/38649550/rails-how-to-disable-turbolinks-in-rails-5
Also, websockets (or WS in Rails?) sounds like a piece of crap:
The same is especially true for WebSocket updates. On poor connections, or if there are server issues, your WebSocket may well get disconnected. If the application is designed to work without it, it’ll be more resilient.
(This was the case when I made Game of Cups - clients constantly disconnected.)
(From Turbo docs.)
I don't want an application "designed to work without" websockets. I want one that works nicely / as intended.
Looked into these and came across some annoying problems which other people seem to have come across too. I don't think SSE are in very wide usage and I think Rails is not designed for them, and for both those reasons, I'm out.
I'm going to start doing this app with short-polling just to get something up and working. I can try and refine short-polling to long-polling or even to something better later. I'll keep turbolinks switched off so that the short-polling stops when we navigate pages.
I had this issue where bundle wasn't recognising the right Ruby version
> bundle
Your Ruby version is 2.6.8, but your Gemfile specified 3.0.6
> rbenv version
3.0.6 (set by /Users/davidmears/projects/games/strategories/.ruby-version)
I got around it with:
> rbenv exec gem install bundler
> rbenv exec bundle
This README would normally document whatever steps are necessary to get the application up and running.
Things you may want to cover:
-
Ruby version
-
System dependencies
-
Configuration
-
Database creation
-
Database initialization
-
How to run the test suite
-
Services (job queues, cache servers, search engines, etc.)
-
Deployment instructions
-
...