Files and folders

The Joppa folder

System	Location
macOS	~/Library/Application Support/joppa
Linux	~/.config/joppa

File or folder	Contents
config.json	Projects, domains, services and settings
processes.json	Project processes, when they’re not in a joppa.toml
running.json	The dev servers Joppa started that are running, to find them again if Joppa closes without stopping them
control.json	Port and token of the local API, for the joppa command (readable only by you)
ca/	The certificate authority: rootCA.pem and its key rootCA-key.pem (read-only)
analytics/	Per-domain stats, one row per minute, kept for 7 days
php/<version>/	Downloaded PHP builds
bin/	The php and composer commands that follow .php-version

The license isn’t in this folder: it’s in the system keychain (service com.getjoppa.license).

In your projects

Joppa only writes to a project what you’ve confirmed:

File	When
.env	Linking a service, HTTPS addresses, editing (always with a diff)
.env.joppa-backup	Copy of the original .env, on the first write
joppa.toml	If you share the processes with the team
.node-version, package.json	If you pin Node or the package manager
.php-version	If you pin PHP
vite.config.*, astro.config.*	If you click Fix the file

Outside these folders

• Shell profile (~/.zshrc…): only the # >>> Joppa (PHP) >>> block, if you turn it on.
• joppa command: a link in /usr/local/bin or ~/.local/bin, if you install it.
• Assistants: the mcpServers.joppa entry in their config, if you connect them.
• Containers: joppa-<engine> and their joppa-<engine>-<version> volumes in your runtime.

Removing everything

Joppa doesn’t have an automatic uninstaller yet. To start from scratch: quit Joppa, remove its containers and volumes (docker rm -f joppa-postgres, docker volume rm joppa-postgres-17…), delete the Joppa folder, and remove the CA from the keychain (macOS: Keychain Access › System › “Joppa local CA”).