Github publish.yml workflow works for web project but not for book project

[esvaralt]

Description

I have two different projects on the same Mac being published on different gh-pages repos. I am attempting. to use the publish.yml process on both (it is just the plain vanilla example publish.yml). quarto render, quarto publish, and quarto publish gh-pages work from both projects to update the published content.
However, 'git push' from main works only for the website project. The repo is updated and gh-pages is updated and published. When publishing to the books site, the workflow errors with

Rendering PDF
running lualatex - 1
No TeX installation was detected.
Please run 'quarto install tinytex' to install TinyTex.
If you prefer, you may install TexLive or another TeX distribution.
WARN: Error encountered when rendering files
ERROR: Error
    at renderFiles (file:///opt/quarto/bin/quarto.js:123710:49)
    at eventLoopTick (ext:core/01_core.js:178:7)
    at async renderProject (file:///opt/quarto/bin/quarto.js:124209:23)
    at async renderForPublish2 (file:///opt/quarto/bin/quarto.js:158561:25)
    at async renderForPublish (file:///opt/quarto/bin/quarto.js:154139:22)
    at async Object.publish2 [as publish] (file:///opt/quarto/bin/quarto.js:154652:24)
    at async publishSite (file:///opt/quarto/bin/quarto.js:158603:38)
    at async publish7 (file:///opt/quarto/bin/quarto.js:158939:58)
    at async doPublish (file:///opt/quarto/bin/quarto.js:158886:7)
    at async publishAction (file:///opt/quarto/bin/quarto.js:158905:5)
Error: Process completed with exit code 1.

'quarto install tinytex' results in 'tinytex is already installed and up to date.' in both projects, and 'quarto check' returns no errors in either project. Workflow permissions are the same for both repos.

Why is the git push workflow working for the website project but not the book project? I know I can just use "quarto publish gh-pages' command, but I would just prefer them both to behave the same way:)

[mcanouil]

Could you share a small self-contained "working" (reproducible) example to work with, i.e., a complete Quarto document or a Git repository? The goal is to make it as easy as possible for us to recreate your problem so that we can fix it: please help us help you! Thanks.

What is "git push workflow" you are talking about?

What publish.yml are you talking about? A GitHub actions? Did you look at the workflow documentation on the repository where it lives?
If you are talking about GitHub Actions, installing TinyTex locally does not install it on the GitHub runner.
TinyTex is required (or another distribution) for PDF/LaTeX format. If your website does not use this format, then of course it's not required.
I suggest reading again the documentation to understand how publishing works.

---

You can share a self-contained "working" (reproducible) Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````).
See https://quarto.org/bug-reports.html#small-is-beautiful-aim-for-a-single-document-with-10-lines.

If you have multiple files (and if it is absolutely required to have multiple files), please share as a Git repository.

R	Python
````qmd --- title: "Reproducible Quarto Document" format: html engine: knitr --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{r} x <- c(1, 2, 3, 4, 5) y <- c(1, 4, 9, 16, 25) plot(x, y) ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````	````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{python} import matplotlib.pyplot as plt x = [1, 2, 3, 4, 5] y = [1, 4, 9, 16, 25] plt.plot(x, y) plt.show() ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````

Additionally and if not already given, please share the output of quarto check within a code block (i.e., using three backticks ```txt), see https://quarto.org/bug-reports.html#check.

[esvaralt]

Thank you - this clarified things for me. I am just starting with quarto. I did the website first, and everything just worked, so that was great. You helped me realize that a difference in the web vs book projects is that the book project has pdf as a format output in addition to the websites html. I did not realize that the pdf rendering would need to take place on the server. I added with: tinytex: true to the publish.yml and now everything is working the way I expect.

Thank you for your guidance.