Skip to content

Uninstall and cleanup

Deleting a project

drupalaibp delete

Run it inside a project to delete that project, or in a parent directory to pick a running project from its immediate subdirectories. It always asks for confirmation, then runs ddev delete -Oy (removes the project's containers, database, and DDEV registration, without keeping a snapshot) and removes the project directory.

delete removes the project only. It leaves behind:

  • DDEV, Docker, and the Docker images they downloaded;
  • the global drupalaibp command and its man pages, if installed;
  • saved configs under ~/.drupalaibp/;
  • anything you pushed to GitHub.

Removing the global command

The global install writes four things; remove them in any order:

rm ~/.local/bin/drupalaibp
rm ~/.local/share/man/man1/drupalaibp*.1
rm -rf ~/.drupalaibp        # saved configs; keep it if you want them

Then delete the PATH block from your shell rc file (~/.zshrc, ~/.bashrc, ~/.bash_profile, or ~/.profile). It is the two lines starting with:

# added by one-line-installer (drupalaibp)

Leave it in place if anything else uses ~/.local/bin; the line is harmless on its own.

Removing DDEV and Docker

The installer does not manage removal of DDEV or Docker. DDEV documents its own removal, including the images it downloaded, at https://docs.ddev.com/en/stable/users/usage/uninstall/. ddev clean --all removes most of what DDEV ever created while keeping DDEV itself.