WordPress security on VIP
Multiple layers of security are in place to protect WordPress applications:
Tag: tech-ref
Showing page 11 of 26
GitHub user access
Every application in the VIP Platform has a dedicated GitHub repository for code development and deploy. The customer will nominate the initial user(s) to be added to their newly created GitHub repository, and a member of VIP will add those users to the GitHub repository with Admin permissions.
Zendesk user access
VIP Support uses the Zendesk ticketing system to receive customer requests and provide support.
WordPress user access
When a new WordPress environment is created, a user account will automatically be created for an individual nominated by the customer organization. The user account on a single site will have an Administrator role, and the user account on a multisite will have a Super Admin role.
Supported character sets and collations
The default setting for DB_CHARSET is utf8mb4, and DB_COLLATE is defined as utf8mb4_unicode_ci on all SQL databases for WordPress VIP Platform environments.
New Relic for WordPress
After New Relic is enabled on a WordPress environment:
New Relic for Node.js
After New Relic is enabled for a Node.js environment, the New Relic NPM package must be installed in the Node.js application.
Databases
Each VIP Platform WordPress environment is supported by a unique database. Unique databases per-environment allows testing to be performed on non-production environments without impacting the production environment.
WordPress on WPVIP
WordPress environments on the WPVIP Platform can be created as either a WordPress single site or a WordPress multisite. WordPress multisite (also known as a WordPress network) allows multiple sites to be created and run from a single installation of WordPress Core files. A copy of VIP Must Use plugins (VIP MU plugins) is loaded on every environment to provide performance enhancements and commonly used plugins like Jetpack and Akismet.
Troubleshooting
If issues are encountered when working with the VIP Local Development Environment, the first troubleshooting step is to verify that the local machine is running up to date versions of VIP-CLI, Node.js, npm, and Docker.