You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to build nbdev docs (nb: docs only, no lib code) based on multiple subfolders - the pattern is as follows:
repo_root
└ nbs_dir
├ sub-directory1
│ ├ core/
│ └ tutorials/nbs/... # here are the tutorials!
├ sub-directory2
│ ├ core/
│ └ tutorials/nbs/... # here are the tutorials!
└ sub-directory3
├ core/
└ tutorials/nbs/... # here are the tutorials!
Thus, I'd like to specify my nbs_path in settings.ini either as follows:
sub-dir1/2/3 are submodules from external libraries which have their own lib code and nbdev tutorials.
This repo would only serve as synced, centralised point to access all tutorials in a single build.
The text was updated successfully, but these errors were encountered:
Not sure i fully understand this solution.
In the repo you are showing the settings.ini still points to the nbs folder only. (https://github.com/fastai/nbdev/blob/master/settings.ini)
nbdev then recursively goes through all the folders inside nbs and generates the docs (i.e., also for the explanations, tutorials, and API folders. (see here: https://nbdev.fast.ai/api)
Yes, that's correct. nbdev recursively goes through the notebooks in the nbs folder. The part where the notebooks differ in the api folder vs the tutorials folder is over here.
When the #|default_exp flag is missing in a notebook, no python file is created for it, and it is rendered by nbdev as docs.
I would like to build nbdev docs (nb: docs only, no lib code) based on multiple subfolders - the pattern is as follows:
Thus, I'd like to specify my
nbs_path
insettings.ini
either as follows:Option 1
Option 2
Additional context:
sub-dir1/2/3 are submodules from external libraries which have their own lib code and nbdev tutorials.
This repo would only serve as synced, centralised point to access all tutorials in a single build.
The text was updated successfully, but these errors were encountered: