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

Using core.cache instead of a cache folder? #57

Open
Jared314 opened this issue Aug 12, 2013 · 2 comments
Open

Using core.cache instead of a cache folder? #57

Jared314 opened this issue Aug 12, 2013 · 2 comments

Comments

@Jared314
Copy link

I'm using memcache (through the Spyglass core.cache implementation) to store rendered items between frontends, but dieter is storing assets on the local file system. I would love to unify that storage.

Are there any plans to abstract the asset caching mechanisms?

@pbiggar
Copy link
Contributor

pbiggar commented Aug 12, 2013

Yes, actually. I've been working on a complete rewrite that supports this better: the idea is that dieter would still compile to the file system, but that it wouldn't actually serve the assets, they'd be served through a CDN, or possibly through some other mechanism like this.

It's a different project because it's not compatible, and breaks a lot of a lot of assumptions in dieter. It's not done yet, but it's maybe 95% of the way there: https://github.com/circleci/stefon.

@vbauer
Copy link

vbauer commented Mar 23, 2014

It would be great. 👍

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