Ah, thanks for explaining that. That makes far more sense. I think in that
case the settings for the cookie should be its own module.

On Tue, Jul 23, 2013 at 10:46 AM, Bennet Huber <notifications@github.com>wrote:

> In deployment/playbooks/assets/local_settings.j2:
>
> > @@ -48,6 +48,8 @@ AUTOCOMPLETE = {
> >      "NE_LNG": {{ autocomplete["nelng"] }}
> >  }
> >
> > +STARREDCOOKIE = {{ starredcookie }}
>
> Since this value is used purely on the client side and nobody is likely to
> want to change it I don't see any advantage to having it stored here. There
> is a hidden cost to adding inconsequential settings to config files, which
> is a 500 config file is very unwieldy (just look at web.config in hunchlab
> for example). I'd rather keep unnecessary values out of settings.py.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/smartchicago/chicago-early-learning/pull/198/files#r5346566>
> .
>