Is it possible to embed a file which is earlier in the file structure?

[louisonsarlinmagnus]

I would like to embed my file to_embed.mdin index.md

My files:

/my_repo
     to_embed.md
     mkdocs/
     |____README.md
     |____mkdocs.yaml
     |____docs/
          |____index.md

index.md:

--8<-- "to_embed.md"

I know that --8<-- "README.md" is working, so the default base_path is set to docs folder.
I've tried with the base_path setting in the mkdocs extension and with a relative path like--8<-- "../to_embed.md" but nothing work around.

So I'm wondering if this is something that's doable, or if I've missed something.

Thank you very much

[facelessuser]

So, you are running mkdocs from the mkdocs folder, not from the root of your project?

[louisonsarlinmagnus]

The only config I've done is in the mkdocs.yaml file.

Here is the configuration:

markdown_extensions:
  - pymdownx.snippets:
      auto_append:
      - docs/glossaire.md

[louisonsarlinmagnus]

This docs/glossaire.md is a file where I store abbreviations

[facelessuser]

Often, I put all of my snippets in a specific folder. If you need to hide it from MkDocs, you can prepend the folder with a .. Anyways, I usually specify some snippets folder, and then any outliers that are not in my direct path, I specify the file directly in the path:

  - pymdownx.snippets:
      base_path:
      - docs/src/markdown/_snippets
      - LICENSE.md
      auto_append:
      - refs.txt

Anyways, in your case, maybe doing something like this would work:

markdown_extensions:
  - pymdownx.snippets:
      base_path:
      - '.'
      - '../to_embed.md'
      auto_append:
      - docs/glossaire.md

Then you can just reference the file with --8<-- "to_embed.md". When you reference a file directly, it can be referenced with just the name, assuming it doesn't conflict with anything else.

Now, I've never actually tested much with .., or I don't recall testing with .., so I'd be interested to hear if it works.

[louisonsarlinmagnus]

I've tried with my project, It didn't work but I've created a simple project with the config above and it seems to work.

I think in my case the problem come from my docker-compose setup.

I will work on it and bring a clear answer !

Thanks for you time 🥇

[facelessuser]

Okay. Yeah, I don't think I do anything that would exclude paths with .., so maybe it is some sort of local environmental issue. Anyways, I'll wait until you can come back with some more info. It sounds like at this point it isn't really a pymdown-extension question as much as it is a Docker question 🙂.