Skip to content
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

Bug when using mkdocs serve -f #37

Closed
timvink opened this issue Dec 15, 2021 · 5 comments
Closed

Bug when using mkdocs serve -f #37

timvink opened this issue Dec 15, 2021 · 5 comments

Comments

@timvink
Copy link
Contributor

timvink commented Dec 15, 2021

I ran into a bug when using mkdocs serve (and mkdocs build) from another directory than the mkdocs.yml file.\

Reproducable example here: https://github.com/timvink/bugreportexample

@rosscdh
Copy link
Owner

rosscdh commented Dec 15, 2021

try absolute path

site_name: My Docs

plugins:
    - search
    - markdownextradata:
        data: /tmp/bugreportexample/{{ cookiecutter.reponame }}/docs/assets
❯ mkdocs serve -f \{\{\ cookiecutter.reponame\ \}\}/mkdocs.yml
INFO     -  Building documentation...
INFO     -  Cleaning site directory
INFO     -  Documentation built in 0.05 seconds
INFO     -  [21:08:44] Serving on http://127.0.0.1:8000/

@rosscdh
Copy link
Owner

rosscdh commented Dec 15, 2021

site_name: My Docs

plugins:
    - search
    - markdownextradata:
        data: ./{{ cookiecutter.reponame }}/docs/assets

also works

@rosscdh
Copy link
Owner

rosscdh commented Dec 15, 2021

I've updated the package to assume config path

24492bc

can you pip install -e at latest.. and if it works then ill make a release

@rosscdh rosscdh reopened this Dec 15, 2021
@timvink
Copy link
Contributor Author

timvink commented Dec 16, 2021

Works 🌟

Thanks! That's a couple less users having to find a workaround :)

@timvink timvink closed this as completed Dec 16, 2021
@rosscdh
Copy link
Owner

rosscdh commented Dec 16, 2021

released https://pypi.org/project/mkdocs-markdownextradata-plugin/0.2.5/

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

No branches or pull requests

2 participants