This is just brilliant, thank you!

I saw your roadmap, FWIW I would put at #1 the Docker artefact - being able to run this without installing/building would make it super useful. It could then also be used in things like github actions for auto documentation as well.

Other ideas:

• [x] Echo the output path used; I was a bit confused when I ran it and nothing seemed to happen - I had to RTFM to find out it went to /tmp by default
• [x] Add ability to specify font used
• [x] Add toggle for displaying dependencies
• [x] Use arrows instead of lines as connectors so that when boxes are moved the connections remain with them

The following line causes warnings https://github.com/etolbakov/excalidocker-rs/blob/4e64a2ab784261f80e2cc13da523e1930139eac9/.github/workflows/release.yml#L234

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

As per Github recommendation a workflow using save-state or set-output like the following

- name: Save state
run: echo "::save-state name={name}::{value}"

- name: Set output
run: echo "::set-output name={name}::{value}"

should be updated to write to the new GITHUB_STATE and GITHUB_OUTPUT environment files:

- name: Save state
run: echo "{name}={value}" >> $GITHUB_STATE

- name: Set output
run: echo "{name}={value}" >> $GITHUB_OUTPUT

source

./excalidocker --input-path ~/git/lakeFS/deployments/compose/docker-compose.yml
thread 'main' panicked at 'index out of bounds: the len is 1 but the index is 1', src/main.rs:159:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Input file is this one

(excalidocker worked fine with this one)

This PR addresses https://github.com/etolbakov/excalidocker-rs/issues/16 Potentially we might need to add edge configuration for connecting arrows as well.

Excalidraw supports 2 edge types: sharp and round. We need to add support in the config. Scope of change:

• add new field in the config
• in the corresponding struct
• in the main method, similar to the background_colour setting

For example:

docker run --rm -e INPUT_PATH=https://raw.githubusercontent.com/treeverse/lakeFS-samples/main/standalone/airflow-dag-example/docker-compose.yml etolbakov/excalidocker:latest > tmp.excalidraw

The generated diagram doesn't show the ports exposed by the services that are extended from a parent Docker Compose, only those in the Docker Compose specified

Also odd how they're all rendered at an increasing vertical offset, not sure if this is by design but keeping it level would be useful too

At the moment network is ignored, it will be good to add network support. At the moment there are 2 options

• have a single colour for all services in one network and paste the agenda.
• wrap all services in one network in a big rectangle with the text that shows network name

It feels that these number of structs is excessive: https://github.com/etolbakov/excalidocker-rs/blob/99459d082a0b413cd0994094f4fcf80f4320ab2d/src/main.rs#L143-L147 During the development I came up with the most straightforward solution and didn't have much time to reflect on the optimal one, but maybe we can reduce the number of HashMap structs.

The code is in relatively untidy state. Commands

cargo check --all-features
cargo fmt -- --check
cargo clippy -- -D warnings	

produce a lot of actions (unused code, not optimal methods etc). This needs to be addressed