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

Publish assets #131

Open
sokac opened this issue May 22, 2014 · 1 comment
Open

Publish assets #131

sokac opened this issue May 22, 2014 · 1 comment

Comments

@sokac
Copy link
Contributor

sokac commented May 22, 2014

AssetManager should have a way to collect all assets during the build process so static content could be deployed to CDN.

Requirements:

  • view helper for static content location (path on development and production will be different)
    • configuration will hold CDN location. Setting this will essentially //disable// AssetManager on production (there won't be any calls to AssetManager as all asset requests will go to CDN).
  • cli controller to collect all static content managed by AssetManager

Any suggestions?

@RWOverdijk
Copy link
Owner

Some ideas:

  • View helper could force internal lookup
  • View helper forcing lookup would mean there's cache busting (based on file contents)
  • Pushing to CDN could be done based on a hook (event?). Custom cacher (which would hook into the resolvers) will be responsible for comparing files.
  • Hook could push files to CDN, and return path / url.

Downsides:

  • You'll have to cache your front-end, or lookups through view helper (you can't have stats on every request.)

@RWOverdijk RWOverdijk mentioned this issue May 28, 2014
Closed
13 tasks
@sokac sokac mentioned this issue Jun 16, 2014
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

2 participants