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

Make cache directory configurable/disableable #1144

Closed
iamed2 opened this issue Feb 12, 2024 · 3 comments
Closed

Make cache directory configurable/disableable #1144

iamed2 opened this issue Feb 12, 2024 · 3 comments

Comments

@iamed2
Copy link

iamed2 commented Feb 12, 2024

I'm implementing a containerized service using Pandoc and Tectonic, and have configured the rest of the document generation pipeline to operate within temporary directories. Unfortunately, even if there is no home directory, Tectonic will attempt to create the home directory, and will use 0777 permissions by default. This caused a bit of a headache, as the container was configured to only allow write access to $TMPDIR, and only OS-level system errors were generated (which did not record what paths were inaccessible).

It does not appear like there is a way to prevent this from happening, or route the cache to another folder. The workaround I have used is setting $HOME to $TMPDIR.

Having a configurable option at the CLI to point the cache at a certain directory, or to disable it, or to force it to operate in $TMPDIR, or to force it to operate in outdir, would be preferable IMO and would have prevented the debugging headache.

@rm-dr
Copy link
Contributor

rm-dr commented Feb 14, 2024

It is possible to change the location of the cache dir with an environment variable, see the bottom of this page.

@iamed2
Copy link
Author

iamed2 commented Feb 14, 2024

Does that environment variable work when using the V1 CLI interface?

@pkgw
Copy link
Collaborator

pkgw commented Feb 15, 2024

@iamed2 I can't think of any good reason why it wouldn't.

@rm-dr rm-dr closed this as completed Sep 20, 2024
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

No branches or pull requests

3 participants