axelson
Scenic Core Team
Is there an easy way to form a BEAM cluster with dynamic membership? Specifically I want to form the cluster from multiple instances of the same escript/program, this means that the name of each node needs to be unique, but names cannot be pre-generated. I could try to connect with sequentially increasing names, but is there an easier/better way? It seems like I could use GitHub - bitwalker/libcluster: Automatic cluster formation/healing for Elixir applications · GitHub but I don’t see a Cluster.Strategy that seems appropriate
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
axelson
Okay, I’ve come up with this little snippet. Is there anything that could be improved with it?
Edit: added a max number
Fl4m3Ph03n1x
From what I remember, PragDave suggests the usage of long names instead of short names for nodes. Unless this is strictly for a local machine, I would go the extra mile and use long names because this way your code will work across different machines.
Another thing I noticed is the usage of
String.to_atom. Depending on your use case, you may want to consider the usage ofString.to_existing_atom(Converting strings to atoms safely - Today I Learned)Thus far, these are the only 2 things I can think about. YMMV but I hope these ideas are of some use to you.
axelson
This is only for a local machine, so I think short names should be fine, in fact if I could I would ignore the hostname completely in this code. Also
Node.start/3andNode.connect/1both only accept atoms so the only way that I see to avoidString.to_atom/1is to pregenerate a set number of node names. Which could be a good idea, but if I were to do that I’d prefer to instead just limit thenumberthatstart_nodewill recurse to, a max of 20 would probably be a good idea.