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"

Temp directory for backups, etc

1. temp/

Resources

• https://www.blog.ajabbi.com/2025/04/data-centre-options-for-pipi-9.html

References

• Reference

Repository

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

Last Updated

30/03/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

Configuration File

data/

• mssql/
• pg/
• 18/

pipi/

• <account type>/
• <account name>/
• com/
• dat/
• log/
• pip/
• <pipi major version>/
• i18n/
• log/
• <pipi version>.txt
• sys/
• temp/
• template/
• _include/
• _layout/
• _log/

• plu/
• tmp/
• www/
• <website1.com>/
• <website2.com>/

temp/

• backups/
• install/
• projects/

Descriptions

Directory	Example	Use (naming)
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.
log	log/	Logs.
pip	pip/	Pipi.
pipi major version	9/ 10/	Production version of Pipi (major version).
pipi version	pipi.9.1.2.34567	ASCII text file (current version).
plu	plu/	Open-source plugins.
tmp	tmp/	Temporary files.
www	www/	All websites.
website.com	wiki.ajabbi.com/	A website (domain name).