Reliability Edit

Once your site is up, how do you keep it that way? And what can you do if it goes down? In most cases, the same best practices apply to WordPress as with other web applications, but some differences and recommendations are detailed here.

Backups

See Backup. If you are looking for more specific documentation, please refer to backing up your database, and backing up your WordPress files.

Top ↑

Monitoring

See Monitoring.

Top ↑

Version Control

See Version Control.

Top ↑

Changelog

  • 2023-06-08: Update the BackupsBackup A backup is a copy of computer data taken and stored elsewhere so that it may be used to restore the original after a data loss event. Backups can be used to recover data after its loss from data deletion or corruption, or to recover data from an earlier time. Backups provide a simple form of disaster recovery., linking to the Advanced Admin.
  • 2023-05-29: Move the MonitoringMonitoring Website monitoring is the process of testing and verifying that end-users can interact with a website or web application as expected. Website monitoring is often used by businesses to ensure website uptime, performance, and functionality is as expected. to the Advanced Administration Handbook.
  • 2023-05-29: Move the Version Control to the Advanced Administration Handbook.
  • 2021-05-27: Fixing infoboxes
  • 2021-02-17: Changelog added
  • 2020-11-23: Minor text changes and info-blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
  • 2020-06-02: Published from GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner.

Last updated: