Deploying built files without a CI service
Typically, the step to build files in a CI service is scripted by the nature of CI tasks. However, if for any reason a CI service is unavailable it is still possible to deploy built files.
Ready to get started with WordPress VIP? Contact us
Showing page 3 of 17
Typically, the step to build files in a CI service is scripted by the nature of CI tasks. However, if for any reason a CI service is unavailable it is still possible to deploy built files.
Custom TLS certificates that are installed for a domain should be renewed by the customer prior to their expiration date. The expiration date for a domain’s TLS certificate is displayed in the column labeled “Certificates” in the Domains & TLS panel of the VIP Dashboard.
The VIP Platform will automatically make attempts to renew a domain’s installed Let’s Encrypt certificate 28 days prior to the certificate’s expiration date.
After a Let’s Encrypt TLS certificate has been provisioned, it is possible to switch to a custom TLS certificate at any time.
When inviting a new user or editing an existing user’s role, the Org role and App role of one of the organization’s other users can be copied and applied to the user being edited.
When an organization configures Single Sign-On (SSO) for their users to log in to the VIP Dashboard, they have the option to Enforce SSO in order to disallow all other authentication methods (e.g., GitHub, WordPress.com).
Single Sign-On (SSO) can be configured as an optional—or enforced—authentication method for an organization’s users to log in to the VIP Dashboard.
The VIP Platform is designed to scale its resources under most conditions, making it generally unnecessary to load test a site. Prior to initiating any load or stress testing, notify VIP by creating a Support ticket and outline the objectives and planned methodology of the load test.
The Network Sites launch tool in the VIP Dashboard can be used to not only launch a site, but to update the Site Address (URL) of a network site to a new custom domain, subdomain, or custom domain with a subdirectory structure.
The VIP Platform is built to support a “code moves up; content moves down” workflow. This means that any new content needs to be added to the production site and then synced down to non-production environments. New code should be tested on the non-production environment prior to introducing it to the production environment.