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

Allow users to specify where they want to store the cache instead of having it hardcoded #190

Open
kamath opened this issue Nov 20, 2024 — with Slack · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

Copy link
Contributor

kamath commented Nov 20, 2024

It seems like a cache directory is created even when caching is disabled. This can become a problem when the library is used in an environment where mkdir is not possible. In the long term, it probably makes sense to allow the users to connect to some external storage / database?
In the short-term, would it be possible to allow the users to specify where they want to store the cache instead of having it hardcoded?

@kamath kamath added the enhancement New feature or request label Nov 20, 2024 — with Slack
@its-jz
Copy link

its-jz commented Nov 20, 2024

Addressed not creating a new directory when enableCaching is set to false here #191

@kamath kamath mentioned this issue Nov 21, 2024
@kamath kamath added this to Stagehand Nov 29, 2024
@kamath kamath added this to the Foundation milestone Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants