in the webform era, we implemented (mostly) the following structure:
- one .NET application (and a corresponding app pool) for all local websites
- in the root of the app, we had a global web.config (managed outside Tridion: connection strings, endpoints,...)
- each 'local' website was a sub-folder (e.g. "/fr_fr" for the french/France website) containing a local web.config holding a set of AppSettings. These AppSettings were mainly fields published from the publication's metadata (e.g. Currency info, culture ID, country code,...).
- our .NET application used a Configuration Facade to easily use the local app settings.
We will now start the implementation of DD4T for one of our clients, and I was wondering what the best approach would be for the 'local web.config' files in DD4T. Any suggestions/best practices to follow?