Skip to content

Conversation

@slusarz
Copy link
Contributor

@slusarz slusarz commented Nov 10, 2025

Unfortunately, all the VitePress PlantUML plugins either display the data by sending to a remote server (plantuml.com), or require Java and the PlantUML JAR to be installed locally.

To keep installation and development of the documentation straightforward, for now require that PlantUML graphics be generated manually. This shouldn't be needed to be done often - and the process to generate is easy if Docker is available.

@github-actions

This comment has been minimized.

@slusarz slusarz force-pushed the fix_plantuml_output branch from 96addd9 to 6db9224 Compare November 10, 2025 21:39
@sirainen
Copy link
Contributor

So .. We have done this for our docs builders?

@slusarz
Copy link
Contributor Author

slusarz commented Nov 11, 2025

So .. We have done this for our docs builders?

Do you mean automatically? It's not intended to be run as part of build process. You need to create a static image as part of a normal, reviewable commit.

@slusarz slusarz force-pushed the fix_plantuml_output branch from 6db9224 to 0a7407c Compare November 14, 2025 19:48
Unfortunately, all the VitePress PlantUML plugins either display the data by
sending to a remote server (plantuml.com), or require Java and the PlantUML
JAR to be installed locally.

To keep installation and development of the documentation straightforward, for
now require that PlantUML graphics be generated manually.  This shouldn't be
needed to be done often - and the process to generate is easy if Docker
is available.
@cmouse cmouse force-pushed the fix_plantuml_output branch from 0a7407c to 5460bde Compare November 17, 2025 06:09
@cmouse cmouse merged commit 4dae04a into dovecot:main Nov 17, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants