DISNIX-VISUALIZE(1)
πΈ NAME πΈ
Bestie, welcome to DISNIX-VISUALIZE(1) β the User Commands manual page thatβs about to make manifest graphs make sense, no cap. The NAME line is literally disnix-visualize - Generate a visualization graph of a manifest. Periodt. π
β¨
π¦ SYNOPSIS π¦
disnix-visualize [OPTION] [MANIFEST]
π DESCRIPTION π
Okay so the command disnix-visualize generates a graph showing services (as nodes), inter-dependencies (as arrows) and target machines (as clusters) from a manifest file generated by disnix-manifest. Itβs giving βmanifest, but make it visual,β fr fr. Obsessed. π
If no manifest file is given, it uses the manifest of the last deployed configuration. Lowkey convenient. π
The graph is exported as dot format, which can be transformed in a raster image format by using the dot command β iykyk, thatβs the transformation step. π
β¨ OPTIONS β¨
-p,--profile=PROFILEβ Name of the profile in which the services are registered. Defaults to:default.--coordinator-profile-path=PATHβ Path to the manifest of the previous configuration. By default this tool will use the manifest stored in the disnix coordinator profile instead of the specified one, which is usually sufficient in most cases.--no-containersβ Do not visualize the containers. Thatβs the whole vibe check: containers stay unvisualized. π«Ά-h,--helpβ Shows the usage of this command to the user.-v,--versionβ Shows the version of this command to the user.
π COPYRIGHT π
Copyright Β© 2008-2022 Sander van der Burg
This page is brought to you by disnix 0.10.2, dated January 1980. Iconic. Slay. Bye bestie! ππ¦π
π¦ where this page comes from
- nixos 26.05: disnix 0.10.2
- nixpkgs unstable: disnix 0.10.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms