Ready to get started with WordPress VIP? Contact us
Showing page 8 of 17
Debugging against a remote environment, such as a VIP Platform environment, can be limiting and challenging. For this reason, it is recommended to debug Node.js application issues on a local development environment. Make an effort to reproduce issues locally, and to keep the local development environment in close synchronization with remote environments.
The VIP Platform supports and strongly encourages the use of the HTTP Strict-Transport-Security response header (HSTS). This header informs browsers that a site should only be accessed using HTTPS , and that any future attempts to access the site using HTTP will automatically be converted to HTTPS.
Media files associated with a WordPress environment can be viewed and downloaded in the application view of the VIP Dashboard.
Environments with Default Deployment enabled are configured to track a specific branch of an application’s wpcomvip GitHub repository. For example, new production environments are set up to track a branch named production by default. Pushing any changes to this branch (via a push, merge, or rebase) triggers an automatic deployment to the production environment.
Testing a reverse proxy‘s configurations should be done with a site’s convenience domain URL in preparation for a site launch. When the proxy testing is complete, and the site is ready to launch, the final production domain (e.g. https://www.example.com) should replace the convenience domain in the configurations.
Reverse proxy configurations should be tested extensively prior to a site launch.
PHP is continuously under development to improve performance and security with every released version. Though every version brings improvements, sometimes new requirements for code syntax or breaking changes are introduced as well.
Node.js applications on the VIP Platform must use npm to manage their dependencies. Other dependency managers such as yarn are not supported.
Database content can be imported or synced to a running VIP Local Development Environment. Before syncing or importing content, It is recommended to first confirm that the VIP Local Development Environment is up and running as expected. Configuring the environment to load locally cloned application code prior to adding data can also help prevent unexpected errors .
By default, Enterprise Search is not enabled for use in the WordPress Admin. Activating the Protected Content feature will send WordPress Admin search queries to Elasticsearch, but also risks exposing non-public content to unauthorized users. The ep_admin_wp_query_integration and ep_ajax_wp_query_integration filters can be used to more selectively enable Enterprise Search for the WordPress Admin.