Q: Dev/Production config settings for client?

[simonh1000]

Is there already a way to implement client side config values during development (e.g. for Google Analytics and Maps API keys). This seems to be a way of doing it that I will use otherwise: http://newtriks.com/2013/11/29/environment-specific-configuration-in-angularjs-using-grunt/

[gintsgints]

I had like same question and ended up using upstart/forever script with all needed variables set as enviroment variables inside deployment host itself.

[kingcody]

@simonh1000 I use jade as an HTML preprocessor and I typically convert index.html to a jade file as well. If that works for you, I'd suggest using express locals bound to config or process.env entries.

[simonh1000]

Thanks for the idea but on this occasion I'm only deploying the client code, so Jade is not an option (unless grunt:build precompiles pages)

[kingcody]

Wow, I must be tired... Grunt actually compiles the jade files on builds and serves, and NOT rendered by express (somehow wasn't thinking about this, only server/views is rendered). You can place your template vars in the grunt config object for the jade task under compile.config.data. You can then use grunt config strings to bind your template vars to your config/env.