tomwang57
I set up the redis adapter according to the doc and deployed it to Heroku where we have 2 dynos running like(I think all dynos start with the same cmd):
elixir --sname server -S mix phx.server
I didn’t set the node_name manually to let it pick the one of --sname:
{Phoenix.PubSub,
adapter: Phoenix.PubSub.Redis,
url: System.get_env("REDIS_URL"),
name: WebInterface.PubSub},
But it didn’t work: messages still not sync between nodes. So am i missing something? Must the node_name be unique for all the dynos/nodes?
Trending in Proposals: Ideas
We are seeing a lot of warning logs like this:
navigate event to "https://someurl" failed because you are redirecting across live_sessio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mwhitworth
Sadly this is not possible unless you use Private Spaces. Dynos are strictly firewalled off from each other
tomwang57
I know we can’t use build-in distributed elixir for pubsub, so according to the doc, we can use redis instead. So it is supposed to work.
mwhitworth
Quite right. My mistake.
My suspicion would be that the sname is not unique for each node (e.g. 127.0.0.1 is often chosen as the host in these scenarios), as you hint at - if you query it for the process on a random dyno, what does it return?
tomwang57
Sorry, my fault. The there was some problem about the redis connection with ssl. After fixing it, it worked.