Skip to main content

DDEV

Aliases inside the web container​

ddev ssh drops you into a container that doesn't have my usual aliases. DDEV copies anything in homeadditions into the container's home directory.

ScopePathCommittable
This project only.ddev/homeadditions/.bash_aliasesYes
Every project on this machine~/.ddev/homeadditions/.bash_aliasesNo

Contents are just normal aliases:

alias ll='ls -alFh'

Restart the project for it to take effect.

ddevinit.sh​

~/.dotfiles/wp-scripts/ddevinit.sh bootstraps a new WordPress project. Run it inside an empty project folder.

What it does, in order:

  1. Prompts for a project name, defaulting to the folder name
  2. Pulls my standard .gitignore from a gist into ./public
  3. Extracts WordPress core from a local zip in the Dropbox update-server folder, no download needed
  4. git init
  5. Interactive plugin picker via fzf. A CORE_PLUGINS list is always copied, then you multi-select any extras
  6. Same again for themes
  7. Configures and starts DDEV, commits, then ddev core install with the standard local admin credentials

The plugin and theme sources come from the Dropbox folder, with a primary path on the external drive and a fallback on the internal one. If it exits early complaining about paths, the external drive isn't mounted.

There's also an older wpinit.sh in the same folder, pre-DDEV.