Add local Kroki fallback configuration for offline builds #69
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#31 Epic: Documentation site polish and sidebar curation
aethyr/Aethyr
Reference: aethyr/Aethyr#69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Metadata
docs: add local Kroki server fallback for offline documentation buildsfeature/m3-v11-docs-kroki-fallbackBackground
The Kroki plugin depends on
kroki.qoto.org. If the service is down, diagrams render as raw code blocks.Expected Behavior
Documentation on configuring a local Kroki instance as fallback, and the plugin reads the Kroki URL from an environment variable.
Acceptance Criteria
KROKI_URLenv var with default fallback tokroki.qoto.orgSubtasks
remark-kroki-inline.jsto readKROKI_URLDefinition of Done
This issue is complete when all subtasks are done, commit created on the specified branch, PR submitted and merged.