You deploy a new PR. It rolls out to all pods. Something breaks. Now you need to rollback, new PR → approvals → deployment time → meanwhile, you're losing customers. With DeployEx? Rollback in 2 clicks. Done ✅.

January news from the Erlang Ecosystem. See what's been going on and upcoming.

marketing.erlef.org/news/email/2...

🎓 5 masterclasses included! Scalability, security, concurrency, AI+Elixir & FP patterns from BEAM legends. Limited tickets:
codebeamvancouver.com#tickets

I just wanted to take a moment to thank you all—DeployEx has just reached 200 stars on GitHub and 1 sponsor. This is an incredible milestone. Community is what makes this project possible. github.com/thiagoesteve...

You need to start engineering your code and think carefully about dependencies. If you reach for a library/framework/shelf solution before understanding what you REALLY need, you may end up with a beautiful front house, but inside...

From dev.to/ndrean/notes... to github.com/thiagoesteve...

DeployEx, Observer Web, and Jellyfish are NOT vibe-coded projects. They've been developed over 3+ years with strong BEAM capabilities, by experienced engineers who firmly believe that BEAM is all you need. You will note many references for 3rd party code in the projects.

With Observer Web and Phoenix LiveView, you get an out-of-the-box metric showing the number of socket connections—in other words, the number of users accessing your system. No code needed, just add Observer Web and watch (or better yet, observe 👀).

Running a migration in your Elixir app—need to run n rounds of deployments to do it properly? Well, if you are using containers, you will have n times of downtime, restarts, disconnections, etc. Use DeployEx and hot upgrades, your app will not restart, go down, change, and your migration will run.

With DeployEx, your deployment has out of the box ObserverWeb, a tool to observe your process relationships, send messages, garbage collect, and much more. It makes debugging very easy to handle and, you don't need DeployEx to have it—you can have ObserverWeb in your app now.

DeployEx got a server restart triggered by Github. Have you ever seen this message: "Hello future GitHubber! I bet you're here to remove those nasty inline styles"? This is an error message from Github due to a timeout, so be prepared because it occasionally happens.

Happy to share 🔊 that DeployEx has received its first sponsor! 🎉 A huge thank you to German Corominas for believing in this project and providing the support that will help our next major release in 2026. Brace yourselves —working on hot-upgrading Elixir while hot-upgrading your app.

Hot upgrades across different OS platforms? 😱

While implementing hot upgrade functionality in DeployEx, I created a release image on Ubuntu 24.04 and hot-upgraded a running release that was originally compiled on macOS —and it worked perfectly!

BEAM is such a powerful runtime. 🚀

DeployEx now has a new feature 🔥 it can hot-upgrade itself 🔥 in three different ways! Let me show you in the video. This feature will be available in the next release, planned for 2026, but you can check it out and test it now in the GitHub repo. Let's spread the campaign #UnstoppableBeam

Is it just me or does anyone else feel like running Elixir apps in production with containers is like buying a PS5 just to run an emulator inside a container to play your game? 🧐

Just received feedback from a team using DeployEx—they love it, with the only inconvenience being the need to restart for new cool features. That feedback just confirmed it: it's time to unlock hot upgrades for DeployEx itself. Work has already begun...Stay tuned!

DeployEx 0.8.0 is released. You can now add or remove replicas, adjust environments, and modify configuration on the fly—all without restarting DeployEx or impacting any running applications.

🖥️ DeployEx (0.8.0)
repo: github.com/thiagoesteve...
changelog: github.com/thiagoesteve...