hubertlepicki
Here’s the thing, I have an umbrella project, with a dozen of OTP apps inside. Currently it’s been deployed to single server. We want to deploy it to multiple nodes and turn this thing to a distributed organism.
While the deployment part seems to be pretty neatly handled by distillery, we’d also like to replicate the production environment as closely as possible locally. This means, we’d like to start the same number of nodes when in development, make sure our global name registrations work and we have things neatly decoupled. This all, while not loosing some of the productivity advantages, like Phoenix code reloader, or assets bundler.
Ideally, I’d go to my umbrella_root/, run a single mix command and it’d bring up the whole system, with N nodes, and M applications running on them.
How would you get this done?
I see two options:
-
Use distillery locally. Write a shell script that builds a distillery :dev release. In theory, I think combination of
dev_mode=trueand a custom watcher for file changes should pick it up, compile, symling the beam files to release directory and this should allow Phoenix auto reload to work. Then, one would need to do the same with assets, start a custom watcher that’d watch, compile assets with bruch and symlink as needed. @bitwalker has this ever been done with distillery?
-
Write a Mix task, that would start N nodes in the cluster, start appropriate applications on each node. This task would have similar code to: distributed_test/lib/distributed_env.ex at master · jschneider1207/distributed_test · GitHub
which is a library that starts N nodes, loads applications there and runs tests in parallel this way.
1 or 2? Or maybe you have better ideas altogether?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
easco
I would recommend something like Terraform (https://www.terraform.io) and a cloud computing provider to fire up actual infrastructure. The same scripts could work in a development environment as they might in a production deployment.
hubertlepicki
Ok, so the solution to the problem above is not to use umbrella project for distributed Elixir application at all.
Instead, use stand alone applications, script it up with custom startup scripts for development.