WordPress for Finance

WordPress for Finance Site Management Explained

102 views August 6, 2018 Leandi Kolver 0

The WordPress for Finance Site Management module is a command hub for launching and managing WordPress sites. It brings a suite of security and control features to the creation and management of your WordPress for Finance instances.

How to create a new site

Create a new site by selecting the plus button.

Edit valid site details in the new site form and select CREATE SITE.

For each new site the followings services are automatically setup on site creation:

  1. Git repository
  2. Development, staging and production site instances
  3. DNS CNAMEs for each site Instance through DNSME
  4. StatusCake uptime monitoring for each site instance
  5. Docker service for each site instance

How to edit site details

The Site Name and Description are the only editable fields within the Site Settings form.

Unlock a site for public view for all site instances within the site settings.

Locking a site from public view will redirect external users to the WP admin login page when they try access the site.

Manage each site instance independently

Every site comes with development, staging and production environments which allows a user to manage and control versions across multidev environments.

Users are able to carry out the following actions within each site instance:

  • Deploy Code – Select a revision of a specific git branch and deploy the code to the site instance.

  • Upload and deploy a database – Select a valid .sql database file from a local drive, upload and deploy the database to the site instance.

An example use case for this facility is when a user needs to download a database backup in order to edit the .sql file and subsequently deploy the updated database to the site instance.

  • Download a backup database – Select and download a database backup stored on our server. The automated backup process runs on a 15 minute schedule. This facility allows users to restore a previous version of the database within seconds if something goes wrong.

  • View and edit the primary domain for the specific site instance

  • Request and view CSR details – Request CSR details by adding valid details into the form and generating the request.

The user can only View CSR details once a CSR has been generated. Once a CRS has been generated, you must copy and submit these details to your certificate authority.

  • Upload TLS certificate – By selecting the ‘Upload TLS’ button, users can paste the TLS certificate details (received from the certificate authority) into the space provided in the form and select ‘OK’ to upload the certificate for the site instance. The expiry date of the last uploaded certificate is displayed below the button.

  • View the DNS details – A DNS record should automatically be generated for each site instance when a new site is created.

  • Enable or disable site instance to Read Only – Switching the site to ‘Read Only’ mode locks down the git repository to prevent anyone from deploying code to the site instance.

  • Enable the production site instance to Live view – Make updates to the production instance without affecting the live production environment. Once updates have been implemented successfully and testing is complete, users can enable to latest changes to the live production environment.

  • Check the Cluster, DNS and Uptime Cluster statuses

The Cluster status represents the docker service status. Using the docker api we are able to confirm the current docker container status which can help us immediately identify if a potential site issue is related to the docker service or not.

The DNS status confirms that a DNS record has been successfully created for a site instance. DNS CNAMEs are auto created for each site instance when a new site is added.

The uptime statistic essentially reflects the website’s availability. StatusCake (external service) runs scheduled tests and monitors that the site instance is up and running without errors.

View Audit Logs

Audit logs enable you to track all user activities across all site instances.

Actions that will be tracked:

  • Create site
  • Edit site setting details
  • Enable or disable site instance for public view
  • Deploy code
  • Deploy database
  • Download database
  • Enable Read Only mode
  • Edit primary domain
  • Request CSR
  • Upload TLS
  • Add redirect
  • Delete redirect
  • Install plugin
  • Uninstall plugin
  • Update plugin
  • Disable or Enable plugin
  • Add IP restriction
  • Delete IP restriction

Was this helpful?