Configurable cache location
See original GitHub issueInstead of the ~/.templateengine/{HostName}
cache location, it would be great if it were configurable by the host.
On VS for Mac, for example, we have an existing cache directory in the more idiomatic location ~/Library/Caches/VisualStudio/7.0
. Similarly in MonoDevelop for Linux, we follow the XDG convention and use ${XDG_CACHE_HOME:-$HOME/.cache}/MonoDevelop/7.0
.
It would be great to be able to put the template cache in a subdirectory of our existing cache location.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Configuration cache
The build cache takes care of caching the outputs and intermediate files of the build, such as task outputs or artifact transform outputs....
Read more >Configure the client cache - Configuration Manager
The default location for the Configuration Manager client cache is %windir%\ccmcache and the default disk space is 5120 MB. Important. Don't ...
Read more >Customize the global cache location
Use one of the following methods to open the Preferences window: · Select the Package Manager category. · Under Packages, open the menu...
Read more >Cache
Locations for the cache. Defaults to path.resolve(cache.cacheDirectory, cache.name) . webpack.config.js const path ...
Read more >Configuration caching deep dive
Configuration caching is a fundamental building block in making builds faster, both from the IDE and the command line.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I do not have rights to reopen this issue, but I think it or #852 should remain open. Dumping stuff into USER_PROFILE is bad and should be considered a bug IMO.
This issue was last touched some years ago. We are working on a new delivery road map. Please reopen if this is something we want & we’ll properly assess its’ priority compared to other work aimed at improving the overall templating UX.