Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation getting to texlive-full #311

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

RadostW
Copy link

@RadostW RadostW commented Nov 10, 2024

Improve quickstart to include texlive-full config

Description

Currently it's hard to find instructions on getting texlive-full running with overleaf-toolkit. Following the manual stops at only a minimal installation.

Contributor Agreement

Add missing information on upgrading to texlive-full
Copy link
Member

@das7pad das7pad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for opening this Pull Request, @RadostW!

https://github.com/overleaf/toolkit/blob/master/doc/ce-upgrading-texlive.md goes into detail how to upgrade TeXLive inside the container.

We prefer keeping the Quick Start Guide to a bare minimum. Does the above "Community Edition: Upgrading TexLive" guide cover everything you need?

To save bandwidth, the Overleaf image only comes with a minimal install of TeXLive. To upgrade to a complete TeXLive installation, run the installation script in the Overleaf container with the following command

```sh
$ docker exec sharelatex tlmgr install scheme-full
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not sufficient anymore. tlmgr path add is required for linking all the bin/ scripts.

@RadostW
Copy link
Author

RadostW commented Nov 11, 2024

"Community Edition: Upgrading TexLive" is good, but it's not easy enough to find it.

My opinion is that without installing some packages (such as babel) community edition is pretty much unusable. For me it's as important as TLS config which is in the quickstart.

I'm not sure "upgrading" is something that a new user would look at when trying to fix packages not working.

Perhaps adding a link to "upgrading texlive" at the end of quickstart is a good compromise? And one sentence why someone would want to "upgrade"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants