Fork me on GitHub

WordPress-kehittäjä, älä missaa ilmaista webinaariamme WordPressin hakutoiminnosta tammikuun 14. päivä!

WordPress-utvecklare, missa inte vår gratis webbinar om sökningen in WordPress den 14. januari!

WordPress developer, don't miss our free webinar about search in WordPress on January 14th!

Example configuration of config.yml

# Configuration for Vagrant

# This is used as the hostname of the Vagrant box
name: wordpress

# These are used for migrating database and uploads back and forth with production
# Comment these out if you don't want this integration
  ssh_port: 12345

  ssh_port: 23456

# Domains are automatically mapped to Vagrant with /etc/hosts modifications
    - wordpress.local

  # If you want others in your local network (e.g. office) to be able to access
  # the site running on your laptop, activate Avahi / Bonjour / Zeroconf that
  # will advertise *.local domains on the network.
  avahi: true

Customizing config.yml


Change name in config.yml to change your site name. This is used in quite a few places in the development environment. Commands like wp-pull-staging-db use this as the username for ssh connections.

For example, with the above config.yml mailcatcher is set up in the address: mailcatcher.example.local.


Add domain and ssh_port to sync with your production instance.


Optional: Add domain and ssh_port to sync with your staging (testing shadow) instance.


Add new domains under domains before you run vagrant up to use extra domains.

See config-sample.yml for more.

Automatic operations on local development startup

The following items help automate typical steps in starting the development environment:

pull_production_db: always
pull_production_plugins: always
pull_production_themes: always

If you want to automatically pull stuff from production use always or set to never to just silence the yes/no question during vagrant up or docker-compose run.