Add VIP config file

configure.php

@@ -653,22 +653,20 @@ function install_plugin( array $plugin_data, bool $prompt, &$installed_plugins )
 		run( 'ln -s mu-plugins/drop-ins/object-cache.php object-cache.php' );
 	}
 
-	write( 'Scaffolding out vip-config...' );
-
-	run( 'mkdir -p vip-config && touch vip-config/.gitkeep' );
-
 	write( 'Scaffolding out VIP directories...' );
 
 	run( 'mkdir -p images && touch images/.gitkeep' );
 	run( 'mkdir -p languages && touch languages/.gitkeep' );
 	run( 'mkdir -p private && touch private/.gitkeep' );
+	run( 'touch vip-config/.gitkeep' );
 
 	echo "Done!\n\n";
 } elseif ( 'pantheon' === $hosting_provider ) {
 	write( 'Deleting VIP-specific GitHub Action workflows...' );
 
 	delete_files(
 		[
+			'vip-config',
 			'.github/workflows/deploy-to-vip.yml',
 			'.circleci',
 		]

vip-config/vip-config.php

@@ -0,0 +1,103 @@
+<?php
+/**
+ * Hi there, VIP dev!
+ *
+ * vip-config.php is where you put things you'd usually put in wp-config.php. Don't worry about database settings
+ * and such, we've taken care of that for you. This is a good place to define a constant or something of that
+ * nature. However, consider using environment variables for anything sensitive or environment-specific:
+ *
+ * @see https://docs.wpvip.com/how-tos/manage-environment-variables/
+ *
+ * WARNING: This file is loaded very early (immediately after `wp-config.php`), which means that most WordPress APIs,
+ *   classes, and functions are not available. The code below should be limited to pure PHP.
+ *
+ * @see https://docs.wpvip.com/technical-references/vip-codebase/vip-config-directory/
+ *
+ * Happy coding!
+ *
+ * - The WordPress VIP Team
+ **/
+
+/**
+ * Redirect non www to www.
+ *
+ * @see https://docs.wpvip.com/redirects/domain-redirects-in-vip-config-php/
+ */
+if ( isset( $_SERVER['HTTP_HOST'] ) && isset( $_SERVER['REQUEST_URI'] ) ) {
+	$http_host   = $_SERVER['HTTP_HOST']; // phpcs:ignore WordPress.Security.ValidatedSanitizedInput.InputNotSanitized
+	$request_uri = $_SERVER['REQUEST_URI']; // phpcs:ignore WordPress.Security.ValidatedSanitizedInput.InputNotSanitized
+}
+
+/**
+ * Set a high default limit to avoid too many revisions from polluting the database.
+ *
+ * @see https://docs.wpvip.com/technical-references/vip-platform/post-revisions/
+ *
+ * Posts with high revisions can result in fatal errors or have performance issues.
+ *
+ * Feel free to adjust this depending on your use cases.
+ */
+if ( ! defined( 'WP_POST_REVISIONS' ) ) {
+	define( 'WP_POST_REVISIONS', 100 );
+}
+
+/**
+ * The VIP_JETPACK_IS_PRIVATE constant is enabled by default in non-production environments.
+ *
+ * It disables programmatic access to content via the WordPress.com REST API and Jetpack Search;
+ * subscriptions via the WordPress.com Reader; and syndication via the WordPress.com Firehose.
+ *
+ * You can disable "private" mode (e.g. for testing) in non-production environment by setting the constant to `false` below (or just by removing the lines).
+ *
+ * @see https://docs.wpvip.com/technical-references/restricting-site-access/controlling-content-distribution-via-jetpack/
+ */
+if (
+	! defined( 'VIP_JETPACK_IS_PRIVATE' )
+	&& defined( 'VIP_GO_APP_ENVIRONMENT' )
+	&& 'production' !== VIP_GO_APP_ENVIRONMENT
+) {
+	define( 'VIP_JETPACK_IS_PRIVATE', true );
+}
+
+/**
+ * Disable New Relic Browser instrumentation.
+ *
+ * By default, the New Relic extension automatically enables Browser instrumentation.
+ *
+ * This injects some New Relic specific javascript onto all pages on the VIP Platform.
+ *
+ * This isn't always desireable (e.g. impacts performance) so let's turn it off.
+ *
+ * If you would like to enable Browser instrumentation, please remove the lines below.
+ *
+ * @see https://docs.newrelic.com/docs/agents/php-agent/features/browser-monitoring-php-agent/#disable
+ * @see https://docs.wpvip.com/technical-references/tools-for-site-management/new-relic/
+ */
+if ( function_exists( 'newrelic_disable_autorum' ) ) {
+	newrelic_disable_autorum();
+}
+
+/**
+ * Set WP_DEBUG to true for all local or non-production VIP environments to ensure
+ * _doing_it_wrong() notices display in Query Monitor. This also changes the error_reporting level to E_ALL.
+ *
+ * @see https://wordpress.org/support/article/debugging-in-wordpress/#wp_debug
+ */
+if (
+	! defined( 'WP_DEBUG' )
+	&& ( ! defined( 'VIP_GO_APP_ENVIRONMENT' ) || 'production' !== VIP_GO_APP_ENVIRONMENT )
+) {
+	define( 'WP_DEBUG', true );
+}
+
+// Enable VIP Search.
+define( 'VIP_ENABLE_VIP_SEARCH', true );
+define( 'VIP_ENABLE_VIP_SEARCH_QUERY_INTEGRATION', true );
+
+// Set up VIP Search locally.
+if ( ! defined( 'VIP_GO_APP_ENVIRONMENT' ) || 'local' === VIP_GO_APP_ENVIRONMENT ) {
+	define( 'VIP_ELASTICSEARCH_ENDPOINTS', [ 'http://localhost:9200' ] );
+	define( 'VIP_ELASTICSEARCH_USERNAME', 'username' );
+	define( 'VIP_ELASTICSEARCH_PASSWORD', 'password' );
+	define( 'FILES_CLIENT_SITE_ID', 'localdev' );
+}