Site won't deploy; "No such file or directory - jupyter"

[lvanveen]

I downloaded the latest version of the alshedivat/al-folio template and followed the instructions in INSTALL.md. In addition, I had to switch the Build and Deployment source (see #1398 (comment)) and add a Repository Secret to insert my Personal Access Token (see #2122 (comment)). After all that, the deployment fails with "converter.rb:58:in `spawn': No such file or directory - jupyter (Errno::ENOENT)" and the error message in the title of this post. I have seen dome discussion around this (see #1545 (comment)) but no solution. I am quite stuck. This happens when running the deployment on GitHub, not locally.
If you have an idea how to fix this, please explain it in detail. I am new to Jekyll so I need some hand-holding.

[george-gca]

Have you followed the recommended approach first? You should first make it work "as is" in your repository, only then make modifications. This way it is easier to keep track of which modifications caused error.

[lvanveen]

Yes, that is exactly what I have done. The only modifications I made are listed in the question. Otherwise, the site repository is as I found it.

[george-gca]

You should use Deploy from a branch, not what is stated in that comment. Note that it takes some time for the GitHub action that does the build and create gh-pages branch to run, which you can check in the Actions tab of your repo.

Also we don't use .github/workflows/jekyll.yml, since we have our own build action in .github/workflows/deploy.yml. That action installs jupyter before building anything. Delete your .github/workflows/jekyll.yml file and try again, changing to Deploy from a branch.

[lvanveen]

OK, I started afresh with a new copy of the template. This time, the first deployment has a couple of red crosses, but a new branch "gh" is created. When I change to deployment from that branch, the red crosses disappear but a new one appears flagging the Lighthouse Badger issue. Adding the PAT as a LIGHTHOUSE_BADGER_TOKEN solves that. I now see the template appear under my URL and can start editing. The only error that keeps coming up now is

---

Run npx prettier . --check
npx prettier . --check
shell: /usr/bin/bash -e {0}
Checking formatting...
[warn] _config.yml
[warn] Code style issues found in the above file. Run Prettier to fix.
Error: Process completed with exit code 1.

---

but it does not seem to stop the process of publishing.

[george-gca]

For this see our FAQ. But yes, prettier errors do not stop the publishing process.