21–30 of 95 posts
This is more for diagramming small graphs. If you are trying to render large networks, there are better alternatives. For OSS graph visualization libraries, check out: - Sigma.js - Vis.js For commercial options: - Ogma (disclosure: my company builds that one) - KeyLines
I liked GraphViz a lot, but eventually got frustrated with its layout algorithms and default look and feel. I would switch to Mermaid wholesale if it could render SVGs without requiring a browser engine.
I’ve personally settled on grapviz (a derivative actually, plantuml) being “good enough” for casual diagrams. Plantuml is built with the idea that it’s for quick and dirty communication, and I think graphviz translates well to this. It’s a nice way to put together a sequence diagram that just helps you understand control flow (and then never took at it again). I have to admit, I haven’t found a more formal programmat…
Example at https://dev.azure.com/itmv/Coffee%20Shop/_wiki/wikis/Coffee-...
Project at https://github.com/Calpano/featdoc
Disclosure: I maintain this project
It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz.
Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, Java app, SSH bastion, Prometheus, grafana, DNS and security groups.
https://github.com/samsquire/mazzle/blob/master/docs/archite...
The tool also parallelises the build based on the graph so for example packer builds can run in parallel.
It also has a GUI but as a tool it's not ready for other people to use.
Earlier quoted context omitted.
Wild, seeing SemVer actually used properly.
You don't need to do a new release for every checkin. You can make a series of breaking changes and only then declare a new release, bumping the version number. After all, it took (at least) 21 years to get from 0 to 3.0.0 There's absolutely no reason for 2 major bumps 11 days apart.
That means you need to postpone the breaking changes for a while, kind of bunching them together. Many projects do that, but it also incurs some cost.
> After all, it took (at least) 21 years to get from 0 to 3.0.0
It's possible that they did not implement semantic changes in the strict sense before and included small breaking changes into non-major releases (I think a lot of software does this). Fast changes of version numbers may just mean they started reflecting each small BC break into the version number.
I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz. Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, J…
I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz. Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, J…
Someone needs to make a multi-OS clone of omniGraffle. I paid €179 for omniGraffle, I’d pay for a multi-OS alternative.
Does omniGraffle accept text input? Because one of the points of GraphViz is text input, which can be easily source-controlled, diffed, machine-generated, etc.
https://support.omnigroup.com/doc-assets//OmniGraffle-Mac/Om...
Earlier quoted context omitted.
Does omniGraffle accept text input? Because one of the points of GraphViz is text input, which can be easily source-controlled, diffed, machine-generated, etc.
Yes Omnigraffle accepted Graphviz files. But uses its own excellent layout engine and allows you to adjust the layout by hand. If you include integration with OmniOutliner, you also get Graffle can also use a wide variety of text based outline file formats. https://support.omnigroup.com/doc-assets//OmniGraffle-Mac/Om...
I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz. Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, J…
Holy macaroni, this is one of the coolest things I've seen in a while. I wonder if a top-level post of this could generate some interesting discussions about other people's exotic approaches to "DevOps", too?
Yes I would love to hear other people's solutions to DevOps problems. I find it an interesting space. There's lots of good ideas but they haven't been brought together.
I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz. Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, J…
I created an analysis compiler that takes intent information and makes it part of the Enterprise DevSecOps pipeline in order to share realtime analysis with the entire organization. As I continued that work, I've also started talking about the feasibility of creating a supercompiler.
GraphViz is the shit, man. It was exactly what I needed to work on this material. You can create your own notation and then couple it with all kinds of tech by way of batch. Highly recommended.*
*The hardest part, frankly, was unlearning all of the other diagramming paradigms I've used. YMMV, but I found GraphViz most useful when you're going completely greenfield.
