Hostmaster 6.x-1.x has the concept of a sites, with some associated fields in the DB, we should work out what they are, and then work out if they should be properties or fields on the entities, and then we should work out which modules they should live in.

Currently 6.x-1.x stores the following about each server:

  • Status:
    • The status currently shows whether the site is enabled or disabled.
  • Language
    • The language the site has been installed in. I am guessing this is set when the site is installed.
  • IP Address
    • The IPv4 address that the site can be accessed from.
  • Database Server
  • Install Profile
    • Which installation profile the site is based on. This is linked to the install profile node within Aegir.
  • Verified
    • A timestamp showing when the site was last verified.
  • Platform
  • Client
    • The client that the site is associated with in Aegir.
  • Encryption
    • If the site is utilizing SSL the word "Enabled" appears, if it is not using SSL, the word "Disabled" appears.
  • Encyrption Key
    • This lists the name of the Encryption Key, SSL Certificate, that you are using for the particular site. E.g. foo.edu
    • It also lists the locations of the key file. "This site is using the SSL certificate and SSL key located at config/ssl.d/foo.edu/openssl.crt and config/ssl.d/foo.edu/openssl.key
  • Domain Aliases
    • Lists the name of the aliases the site can be accessed from. These are ServerAliases that are added in the sites .conf file.
  • Redirection
    • The word "Yes" is shown if redirection is turned on. "No" is shown if redirection is turned off.
  • Cron Run
    • A timestamp indicating when Cron was last ran successfully.

Comments

themusician’s picture

themusician commented
Issue summary: View changes

I have attempted to document what the current 6.x branch stores about each site.

themusician’s picture

themusician commented

Hi all,

I attempted to determine what Aegir tracks about each site. I need to read up about fields vs. properties before I can propose any structure for the 7.x branch.

themusician’s picture

themusician commented

After reading up on fields vs. properties of entities I believe fields are user editable components, and properties are referenced from other entities. If that is the case, here is my proposed structure.

Status - Property

Language - Property
Populated based on information provided by the site.

IP Address - Property
Pulled as a reference to the server the platform exists on.

Database Server - Field
Users are able to select the DB server the site should use.

Install Profile - Property
Based on the platform the site is installed on.

Verified - Property

Platform - Field
The user chooses which platform to install the site on.

Client - Field
Should this support multiple clients? Say an administrator client and the site owner?

Encryption - Field
Turn SSL on or off.

Encyrption Key - Field
This should be exposed to the user so that they can specifically specify what SSL certificate to use. https://drupal.org/node/1126640

Domain Aliases - Field
Currently users can list as many aliases as they want.

Redirection - Field

Cron Run - Property

steven jones’s picture

steven jones commented

Ah, not quite, so properties are basically just columns in the base table for the entity, you have to provide the UI for editing and viewing them, unlike fields. But thanks for the list, that's great!

steven jones’s picture

steven jones commented
Status: Active » Postponed
helmo’s picture

helmo commented
Version: 7.x-2.x-dev » 7.x-3.x-dev

Moving to 7.x-3.x version tag (7.x-2.x never existed, we went for 6.x-2.x).

helmo’s picture

helmo commented
Issue summary: View changes

Added h2 to the section title.