Relative paths to icons in CI/CD environment #7322
Unanswered
NikosAlexandris
asked this question in
Q&A
Replies: 1 comment 4 replies
-
I am not sure why the paths are different on the CI system? Note that MkDocs only copies files to |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. When I build some documentation locally, it all works fine and I can see for example diagrams generated within executable code blocks (using https://pawamoy.github.io/markdown-exec/) and make use of custom icons/logos, rendered properly. When the same build process runs via a CI/CD in a GitLab, the diagrams fail to build/render simply because the icons/logs are not in the right directory.
I am lost as to where does the change of the root directory of all files related to the documentation are copied! I have locally my files under
docs/icons
and I use then inside some Markdown file (e.g. under/indocs/icons/source_code/architecture.md
) likecustom_icon =
../icons/some_icon.png. In the CI/CD container these are copied and available under the
/` path, for example :Locally
CI
So, if an image is set to be found under
../icons/some_icon.png
why does this relative path not work in the CI ?What should I take care to do in order to get relative paths work ?
Is any bit from the configuration file relevant ?
ps- I 've seen a couple of issues mentioning relative paths, but I am still a bit lost on this.
Beta Was this translation helpful? Give feedback.
All reactions