-
-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set mermaid configuration #1326
Comments
Hello Guillaume, Technically, that's possible now that we accept a list of options and propagate them to the companion containers. Lines 11 to 36 in 5023863
Then, we will need to update the Mermaid default config: Lines 5 to 32 in 5023863
Do you want to give it a try? |
Thanks, looks feasible. I don't have the bandwidth to do it right now, so if anyone reading this wants it they should not rely on me implementing it. |
interested in this but from a different perspective, i'd like to be able to set kroki to have a default set of options for a given engine, or perhaps even a given referrer? ie, if wiki.mydomain.com calls a kroki diagram up, it can go 'oh, yep, the theme for that is this'. |
Hi, I am a backstage user and I have the same requirement. I will make an attempt to implement this. Just one thing I need help on @Mogztter . How do I run the EDIT: |
I have created a PR which partially fulfills this issue. For now, it will pretty much work with only |
Yes, the "gateway" server is a Vert.x stateless web app. You can indeed run the main 😉
Thanks for contributing!
I will have a look this week-end 👍🏻 |
Mermaid has a bunch of features that need to be set at configuration level, such as
mainBranchName
for gitGraph.Would it be possible to change mermaid configuration in a HTTP call?
The text was updated successfully, but these errors were encountered: