There are two common approaches for configuring web
applications:
- Configuration file(s) in the web application's directory
- Storing configuration data in the database
What sort of data am I talking about:
- Email setup (where to send response form, error emails etc, whether to send mail to customers etc)
- Setup of things which need to vary between development and production - payment service provider configuration, setup of other third party integration things
- Error handler configuration (whether to display errors, where to log them, email them etc)
- Enabling / disabling features (for example, debug things)
- Visual stuff or branding (labels etc)
Clearly the database connection string needs to be stored
somewhere too, but that can't be in the database for obvious
reasons.
…