build process - How to automate generation of SVG file with Graphviz? -


i decided start project website. website published through github pages.

my website include svg file. svg file generated graphviz dot-file. idea modify information displayed in svg, users can change definition of dot-file, graphviz re-generate svg, , new svg image automatically displayed once web page served.

however, left in uncomfortable situation of requiring contributors edit dot-file run script calls graphviz, , commit changes both svg and dot file.

if contributor changes dot-file, forgets run graphviz script, commits, repository contain dot-file , svg inconsistent each other.

i can't not track versions of dot-file, because svg gibberish - dot-file human-editable definition. can't not track svg, because, how else stay date , available github pages consumption? , yet, both of them tracked, keeping track of changes in redundant manner, , introducing opportunity conflicts. it's bit versioning both c code and compiled .exe. silly.

what's best way of making sure whenever dot-file edited, svg stay concurrent it? need rethink strategy?

you might consider setting jenkins instance this. create job triggered change in dot file (using git plugin). job execute dot command , commit new svg file.


Comments

Popular posts from this blog

user interface - How to replace the Python logo in a Tkinter-based Python GUI app? -

objective c - Greedy NSProgressIndicator Allocation -

how to set an OCR language in Google Drive -