Updates comments

config/application.php

@@ -1,4 +1,12 @@
 <?php
+/**
+ * Your base production configuration goes in this file. Environment-specific
+ * overrides go in their respective config/environments/{{WP_ENV}}.php file.
+ *
+ * A good default policy is to deviate from the production config as little as
+ * possible. Try to define as much of your configuration in this file as you
+ * can.
+ */
 
 use Roots\WPConfig\Config;
 
@@ -75,8 +83,7 @@
 Config::define('DISALLOW_FILE_MODS', true);
 
 /**
- * Safe Debugging Settings
- * Override these in config/{WP_ENV}.php
+ * Debugging Settings
  */
 Config::define('WP_DEBUG_DISPLAY', false);
 Config::define('SCRIPT_DEBUG', false);

config/environments/development.php

@@ -1,5 +1,5 @@
 <?php
-/** Configuration Overrides for Development */
+/** Configuration overrides for WP_ENV === 'development' */
 
 use Roots\WPConfig\Config;
 
@@ -8,3 +8,6 @@
 Config::define('SCRIPT_DEBUG', true);
 
 ini_set('display_errors', 1);
+
+// Enable plugin and theme updates and installation from the admin
+Config::define('DISALLOW_FILE_MODS', false);

config/environments/staging.php

@@ -1,7 +1,15 @@
 <?php
-/** Configuration Overrides for Staging */
+/**
+ * Configuration overrides for WP_ENV === 'staging'
+ */
 
 use Roots\WPConfig\Config;
 
-// Config::define('WP_DEBUG', true);
-// ini_set('display_errors', 1);
+/**
+ * You should try to keep staging as close to production as possible. However,
+ * should you need to, you can always override production configuration values
+ * with `Config::define`.
+ *
+ * Example: `Config::define('WP_DEBUG', true);`
+ * Example: `Config::define('DISALLOW_FILE_MODS', false);`
+ */