Ready to get started with WordPress VIP? Contact us
Showing page 1 of 16
Custom Deployment enables application code to be developed in a version control system outside of an application’s wpcomvip GitHub repository. Repositories outside of the wpcomvip GitHub organization cannot utilize CircleCI supplied by WordPress VIP, but they are also not limited to CircleCI and any type of continuous integration and/or a continuous deployment (CI/CD) method can be utilized instead.
Important Alerts are automated Notifications that are sent to communicate time-sensitive information that potentially affect an organization and some or all of its applications or environments.
The Custom Deployment method enables application code to be developed in a version control system outside of an application's wpcomvip GitHub repository. The developed code can then be deployed to a VIP Platform environment with VIP-CLI or a continuous deployment method.
The Default Deployment method deploys code from a branch of an application’s wpcomvip GitHub repository to a configured environment. Default Deployment is enabled for all environments of WordPress applications and Node.js applications by default. WordPress application environments can optionally enable the Custom Deployment method to deploy code that was developed outside of a wpcomvip GitHub repository.
By default, transactional emails (e.g., password resets, user registration notifications) are sent from the email address donotreply@wpvip.com. The default sender’s email address can be overridden with an SMTP plugin or custom code to send emails from a custom domain instead.
Log error files for a GitHub Codespace environment can be accessed in the terminal of the Visual Studio Code interface.
The vip-sync-db command can sync the database of a WordPress VIP Platform environment to a codespace environment that was created with the .devcontainer/devcontainer.json file provided by WPVIP.
Managing environment values with the VIP-CLI vip config envvar command is for VIP Platform environments only, and cannot be used on a VIP Local Development Environment. Manage environment variables on a VIP Local Development Environment by manually adding them as a defined constant instead.
The .devcontainer/devcontainer.json file provided by WordPress VIP can be modified to customize the available features and settings of a codespace environment. Settings defined in the features section of the file allow customers to optionally enable features such as Elasticsearch, Xdebug, Photon, and MailPit, or specify a version of PHP.
Only SQL database files that were exported from a WordPress install can be imported to a running codespace environment. For environments that are hosted on the VIP Platform, SQL database backup files can be downloaded from the application’s VIP Dashboard.