[Idea] Self Hosting, co-located Diagrams

[StevenLangbroek]

Is your feature request related to a problem? Please describe.
Right now, the modeler has no opinions about storage: open in browser, upload a .dst file, and export when you're done. That works really well, but is also quite limiting for an organization of our scale. We prefer colocating diagrams with the systems they apply to (where possible).

Describe the solution you'd like
I could imagine being able to run a command like npx modeler --src=./domain , hosting the server at a specific port, with a sidebar that allows folks to open any .dst files from the ./domain folder, and being able to save them with a single click (or automatically on editing, but that's a detail).

Additional context
It's just an idea at this point, but I'd love to hear what y'all think, or if something like this has been discussed before / is under development.

[hofstef]

Hi, we have briefly discussed if the modeler can be embedded in a VS-Code-like environment that provides file management, git integration, etc. In this scenario, several domain stories could share a common icon set and glossary which makes it better suited for power users. But we have no detailed plans yet.

[almereyda]

VS Code supported is tracked in #130

[StevenLangbroek]

@hofstef sorry if this is blunt, but is WPS planning to meaningfully maintain this package or not? The community has been reporting the frustration of losing state when the browser closes for a long time now, and all I hear about is vague plans of what appears to be a stalled rewrite in a framework that is notoriously hard to get into, and losing marketshare as well as user satisfaction. It seems the only person working on this has flamed out somewhere around January outside of a logo update of WPS, the sponsor of the project. I'm hesitant to dedicate any of my or my team's time to it, despite being an avid user, because of the lack of clarity around this project's future. Can you help me understand what a productive path forward looks like here? Heck, I'd even pay for this product to fund baseline functionality, as enthusiastically as I've paid for Structurizr in the past. This thing is good, please don't let it die because of ambition that is out of step with reality.

[hschwentner]

Hi @StevenLangbroek, thanks for both being persistent and keeping the faith to Egon.io!

WPS wants to (and I would argue often does) meaningfully maintain the tool. We've just added a possibility to chooses between V1 and V2-beta on https://egon.io and the release of V2 will not take a long time (or at least I hope so).

As for the funding, we have to think through the possibilites here (GH Sponsors, Patreon, ...).