Allow content that is not in a subdirectory of the book
See original GitHub issueI would like to organize my project like this:
TopLevelOfRepo
mybookname
_toc.yml
notebooks
chap00.ipynb
In _toc.yml
, I expected to be able to write
- file: ../notebooks/chap00
But that doesn’t work – it says it can’t find chap00.ipynb
.
Is there a reason for this restriction? Or am I doing something wrong?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:17 (8 by maintainers)
Top Results From Across the Web
How do I put Bookdown chapters in a subdirectory?
I can't figure put how to make a book with Rmd files in a subdirectory. Here's my current directory structure: myProject.Rproj; index.
Read more >8.5. Controlling the Contents of an Assembly - Sonatype Help
Since a directories' execute permission is what allows users to list their contents, we want to make sure directories are executable in addition...
Read more >Subdirectory Setup - BookStack
First, You will need to choose a folder to install BookStack into. This should be a separate directory from where your main website...
Read more >Keep Subdirectory Structure in Dockerfile Copy | Baeldung
Let's understand the content line by line: the first line states that we're using the latest ubuntu image as our base image; the...
Read more >You can change permissions for all files in a directory. - O'Reilly
This command gives the owner read/write permissions for the file called who. out. The letter u represents the owner (user), and +rw adds...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@redelmann Since opening this issue, I have found that I actually prefer to copy files from other directories into my jupyter-book build directory. In some cases I have to change file names; in other cases I run scripts to make changes in the notebooks themselves. And it helps me keep versioning straight. Not sure if this helps with your use-case, though.
Just a quick note on cluttering up the repository. @AllenDowney you mentioned that Jupyter Book will create a lot of extra files - just a note that these will all be in a
_build
folder, and generally speaking you wouldn’t include that folder with your github repo anyway (usually folks set up a github action to auto-deploy the repo to a website or something, see here for some ideas).That means your repository on github could just look like
and when you build the book, it would create a
_build
folder that you wouldn’t need to check into git. That’s the only folder that Jupyter Book will generate. (this is different from what Jupyter Book used to do, which included all of the files for a Jekyll website in the root of the repo, but it now uses Sphinx so we don’t have to do that anymore 😃 )Just wanted to clarify that in case it wasn’t clear!