Alex66
Visual hierarchical graph editor that generates configuration.nix and deploys via nixos-rebuild switch.
- Nodes are Nix fragments
- Gateways descend into subgraphs (floors)
- NixOS merges the composed fragments automatically
- One-click deploy to a real NixOS machine
- OODN registry for ambient config (hostname, timezone, stateVersion…)
- Pre-built stacks (Grafana+Prometheus, Web Server, etc.)
Built with Elixir/Phoenix. Early stage but working end-to-end.
Looking for feedback, improvement ideas, and anyone interested in contributing templates or backends.
All discussion welcome.
GitHub:
Trending in Announcing
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
I needed to reuse React components from my Chrome extension in my Phoenix/LiveView backend. I noticed that for Svelte/Vue, there are live...
New
I released Doggo, a collection of unstyled Phoenix components.
https://github.com/woylie/doggo
Features
Unstyled Phoenix components....
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
Hello
Published a new library - ProcessHub!
ProcessHub is a library designed to manage process distribution within the Elixir cluster. ...
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
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
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
It’s not that it’s vocabulary is too advanced. It’s something worse.
I get lost trying to follow even a paragraph written by Claude. It’...
New
This showed up on my feed.. anyone heard of it? Just hype?
Ox Alpha is a reasoning model designed for coding, sustained ag...
New
Today we’re releasing Oban for Python. Not an Oban client in Python. Not a pythonx wrapper embedded in Elixir. Nope, it’s a fully operati...
New
@hugobarauna, Dr. Dimitrios Koutmos (my brother) and I (Alex Koutmos) have been hard at work on writing a book on how you can use Elixir ...
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
- #elixirconf-us
- #ai
- #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 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
Hi Alex!
The description reads nice, I am searching for a nicer config editor for a while already!
Some screenshots here and/or in the README would be nice. I barely can imagine how this might look like in practice, and at the same time, I can not just try it out, as my NixOS setup is… Not quite the norm.
Also are flakes supported or flake support planned?
Alex66
Here dev.to article with screenshot Tomato
Flakes support is not yet implemented — currently targeting classic configuration.nix — but it’s high on the roadmap. The backend is pluggable so it’s a natural next step. What’s your NixOS setup if you don’t mind sharing?
NobbZ
https://github.com/NobbZ/nixos-config
Alex66
That’s a beautiful config — exactly the kind of complexity Tomato aims to make navigable visually. Flakes support is the clear gap right now.
With flakes you’d have per-host graphs, shared module subgraphs reused across machines, home-manager as another floor.
That’s the roadmap. Mind if I use your config as a reference for the flakes backend design?
Alex66
For Tomato v0.2 flake support, the Walker needs a FlakeBackend that generates:
This is totally doable with the current architecture. The DAG model already supports it — it’s just a different finalize function.
NobbZ
Sure, though especially the flake parts abstraction I have spun around it, might make things a little less easy