Discussion:
[AngularJS] Best practice (not)caching partials on prodution
Dennis O
2015-07-28 15:08:53 UTC
Permalink
Hi,

Currently having an issue with partials cached and not updated on different
actions.
However, option of removing cache completely, for ex. with
$templateCache.removeAll(); , seems like a bad idea.

I'm running nginx, can add Varnish to the setup for this setup if there's
any advantage.

Please share your experiences dealing with partials caching on production,
when a site is dynamic, i.e. partials are supposed to reflect data changes.

Thank you!
D.
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angular+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
Sander Elias
2015-08-02 18:40:03 UTC
Permalink
Hi Dennis,

I think the best way to do what you are asking is to use a build tool that
encapsulates your templates into a JS file (use a tool like
Angular-templateCache
<https://github.com/miickel/gulp-angular-templatecache>)

Regards
Sander
--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angular+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
Loading...