Pages

▼

About

▼

Enterprise plan directory structure

Mike's Notes

Pipi 9 is still highly experimental. I have been very busy over the last month working on the second deployment of Pipi 9 to production.

  • The first (dogfooding) is Ajabbi.com.
  • The second (pilot) is for a national disability rights organisation in NZ.

The second has been very slow, mainly because it involved the migration of an existing website to a new one, which required careful consideration of the organisation's needs, including using 4 languages (English, Maori, NZ Sign Language, AAC), catering for screens-formats (mobile, desktop, braille, screenreaders, kiosk, TV), and personalised profiles to meet accessibility needs. There have been six months of extensive experimentation and user testing using a manually created 1,100-page static website prototype. Last week, the successful import of existing content into a CMS database was completed. The job now is to connect Pipi 9 to this database to automate future production of all website content.

These notes are about the draft default directory structure for that website. All other 26 existing websites have now been migrated to use the same default structure.

Update 30/03/2026

Putting the data centre into production has resulted in some changes.

Data directory for databases external to Pipi
  1. data/
  2. <Database Type>/ eg "pg"
  3. <Database Version No>/ eg "18"

Pipi directory

  1. pipi/
  2. <Account type>/ eg "e"
  3. <Account Name>/ eg "ajabbi"
Work directory for backups, etc
  1. work/

Update 04/04/2026

Pipi Robot added to description.

Update 06/04/2026

<major version><edition><account type>/ added to all configurations to standardise and simplify setups.

Update 11/04/2026

Pipi Nest is used as the name for the root config.

Update 15/04/2026

<account name(s)> AND <instance name(s)> both present.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

23/04/2026

Enterprise plan directory structure

By: Mike Peters
On a Sandy Beach: 18/08/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

This is the current default directory configuration for enterprise plan customer accounts. It should also work for the digital twins in the Pipi 9 data centre.

The account administrator can edit the configuration file to easily change the location of these key directories for a particular cloud host.

  • AWS
  • Azure
  • GCP
  • IBM
  • Oracle
  • etc. 

On a public-facing website, all of this would be obfuscated using UUIDs, hidden keys, etc.

Pipi Robot

The hidden robot contains most of the complex systems and functions and acts as the super-administrator, thereby simplifying enterprise applications.

Configuration File

/9ae/ (Pipi Nest)

  • pipi_nest_probe.cfm
  • data/
    • couchbase/
    • db2/
    • derby/
    • h2/
    • hsqldb/
    • informix/
    • mariadb/
    • msaccess/
      • 32/
      • 64/
    • mssql/
    • mysql/
    • oracle/
    • pg/
      • 18/
    • sqllite/
    • sybase/
    • virtuoso/
  • pipi/
    • Application.cfc (1) - Nest settings
    • pipi_nest.cfm
    • ajabbi/ (Account Name)
      • Application.cfc (2) - Account settings
      • pipi_account.cfm
      • com/
      • dat/
      • lib/
      • log/
      • plu/
      • tmp/
      • www/
        • learn.ajabbi.com/
          • Application.cfc (4) - Website settings
        • wiki.ajabbi.com/
          • Application.cfc (4) - Website settings
    • dis-01/ (Instance)
    • ...
    • dis-04/ (Instance)
      • Application.cfc (2) - Account settings
      • pipi_account.cfm
      • pip/
        • Application.cfc (3) - Version settings
        • pipi_version.,cfm
        • i18n/
        • log/
        • pipi_<pipi version>.txt
        • sys/
        • temp/
        • template/
          • _include/
          • _layout/
            • _log/
      • www/
        • mission-control/
          • Application.cfc (4) - Website settings
  • work/
    • backup/
    • install/
    • project/

    Descriptions


    Directory Example Description
    <major version><edition><account type> 9ae/ Pipi Nest:
    Major version = 9
    Edition = a (Pipi Application)
    Account type = e (Enterprise).
    <account name> ajabbi/ User account codename (lowercase, unique ASCII).
    com com/ Open-source code packages from GitHub.
    dat dat/ Customer data.
    lib lib/ Code libraries.
    log log/ Logs.
    plu plu/ Open-source plugins.
    tmp tmp/ Temporary files.
    www www/ All websites.
    <website> wiki.ajabbi.com/ A website (domain name).
    <instance name> dis-01/ Pipi instance name (retired deity, lowercase, unique ASCII).
    ,

    No comments:

    Post a Comment