Keep development and production settings distinct

Set the site's environment intentionally and inspect the resolved value before relying on environment-specific tools. Development behavior can include trace controls, extra browser output, and asset settings that are unsuitable for normal visitor traffic.

Keep credentials outside shared documentation and committed examples. Give local installations their own database and hostname so an ordinary test cannot target the production site by accident.

Exercise the release configuration in an acceptance environment before deploying it. Compare the resolved settings, enabled modules, and storage paths when behavior differs between environments.