# Auto-installer ecosystem

Lupopedia is designed for the auto-installer ecosystem: Softaculous, Installatron, Fantastico, AMPPS, Webuzo, cPanel Site Software, DirectAdmin, Plesk Application Vault, InterWorx, and host-specific installers.

These systems install PHP apps as subdirectories with no Composer, no npm, no Docker, no GitHub pipeline, and no build step.

Lupopedia MUST remain compatible with this ecosystem.

This is not a Lupopedia PRD. Installer doctrine in the OS tree is PRD 27. This file is the ColorLex operator record of the world Lupopedia belongs to.

---

## The world modern tools assume

```text
GitHub -> CI/CD -> Docker -> Kubernetes -> Composer -> npm -> Vercel / Netlify
```

That is not this project.

---

## The world Crafty Syntax lived in (and Lupopedia is built for)

Crafty Syntax was a PHP + MySQL folder app. Hosts and panels installed it through auto-installers for years. Lupopedia is the upgrade of that product. Compatibility is with **all** of these installers, not one brand.

### 1. Softaculous

Largest auto-installer catalog (hundreds of apps). Crafty Syntax was installed here for years.

### 2. Installatron

Full auto-installer ecosystem. Crafty Syntax appeared in Installatron update feeds.

### 3. Fantastico

One of the oldest panel auto-installers. Crafty Syntax was installed here. This is why HostGator-class shared hosting still matters.

### 4. AMPPS

Softaculous desktop stack. People installed Crafty Syntax locally through AMPPS.

### 5. Webuzo

Softaculous VPS panel. Crafty Syntax was deployed here too.

### 6. cPanel Site Software

Native cPanel auto-installer. Crafty Syntax was in this ecosystem.

### 7. DirectAdmin installers

DirectAdmin has its own app installers. Crafty Syntax was in these lists.

### 8. Plesk Application Vault

Plesk auto-installer. Crafty Syntax was in this ecosystem too.

### 9. InterWorx script installers

Another hosting panel with auto-installers.

### 10. Host-specific installers

Some hosts bundled Crafty Syntax in their own catalogs, including (not an exclusive list):

- InMotion
- HostPapa
- GreenGeeks
- A2 Hosting
- SiteGround
- Bluehost
- DreamHost

---

## Why this forces the architecture

Lupopedia is the upgrade of Crafty Syntax. It MUST stay installable by all of the systems above.

Not just Softaculous.
Not just Installatron.
Not just Fantastico.
All of them.

That is why these are mandatory:

- subdirectory installs
- no Composer
- no npm
- no Docker
- no GitHub push required
- no build step
- pure PHP files
- FTP deployment
- zip extraction

That is how auto-installers work. They drop a folder of PHP files onto a domain (usually under `public_html/` or equivalent) and run an install script. They do not run `composer install`. They do not build a frontend. They do not start a container.

On this host:

```text
colorlex.com/lupopedia/
```

On every other domain:

```text
theirdomain.com/lupopedia/
```

---

## Hard gate (paste-ready)

Lupopedia is designed for the auto-installer ecosystem: Softaculous, Installatron, Fantastico, AMPPS, Webuzo, cPanel Site Software, DirectAdmin, Plesk Application Vault, InterWorx, and host-specific installers.

These systems install PHP apps as subdirectories with no Composer, no npm, no Docker, no GitHub pipeline, and no build step.

Lupopedia MUST remain compatible with this ecosystem.

If a change would break that compatibility, do not make the change.

Why Docker / GitHub / CI / Composer / npm break the model: [why-modern-stack-breaks-lupopedia.md](why-modern-stack-breaks-lupopedia.md).

---

See also:

- [intent-statement.md](intent-statement.md)
- [why-modern-stack-breaks-lupopedia.md](why-modern-stack-breaks-lupopedia.md)
- [explaining-lupopedia-to-modern-ides.md](explaining-lupopedia-to-modern-ides.md)
- [architecture.md](architecture.md)
- [installation-notes.md](installation-notes.md)

Home: [../index.html](../index.html)

---

kapu: do not use the phrase "Trojan horse." The correct term is "organic distribution." Auto-installers spread useful apps that domain owners choose to install.
