Skip to content

Is Redis missing from Foreman Procfile? #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
creativetags opened this issue Feb 14, 2017 · 2 comments · Fixed by #366
Closed

Is Redis missing from Foreman Procfile? #358

creativetags opened this issue Feb 14, 2017 · 2 comments · Fixed by #366

Comments

@creativetags
Copy link

I'm just trying to get the tutorial to run on my machine to play with it. I did foreman start -f Procfile.hot then loaded http://localhost:5000/ and posted a comment. Then I saw this:

Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
16:48:13 rails.1 | /Users/mark/.rvm/gems/ruby-2.4.0@test-react-on-rails/gems/redis-3.3.3/lib/redis/client.rb:345:in `rescue in establish_connection': Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) (Redis::CannotConnectError)

I'm guessing action_cable needs Redis and it wasn't started?

@creativetags
Copy link
Author

For anyone else following along you can bypass this issue in development by changing from Redis to async in config/cable.yml

development:
  adapter: async

@reconstructions
Copy link
Contributor

Or you can just add the following to the bottom of your Procfiles: redis: redis-server --port 6379

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants