It is not recommended to change the configuration in
Vagrantfile. The file should only be used to toggle the beta version of the Vagrant box.
config.yml file in the project directory is used to set up the local development environment.
Seravo sites should come with one pre-configured. When you run the site for the first time with an
empty project template, the default
config.yml file is generated from
name: wordpress development: domains: - wordpress.local
name: wordpress production: domain: example.seravo.com ssh_port: 12345 development: domains: - mywpsite.local - another.local - third.mywpsite.local pull_production_db: never pull_production_plugins: never pull_production_themes: never
name in config.yml to change your site name.
This is used in quite a few places in the development environment.
wp-pull-staging-db use this as the username for ssh connections.
ssh_port to sync with your production instance.
production: domain: example.seravo.com ssh_port: 12345
ssh_port to sync with your staging (testing shadow) instance.
staging: domain: example.seravo.com ssh_port: 23456
Description: List of the local domains to create. Multisites should add all domains to the list. These must not conflict with any other locally running site.
development: domains: - mywpsite.local - another.local - third.mywpsite.local
Description: Whether to automatically pull from production on
vagrant up. Set to
development: pull_production_db: always pull_production_plugins: always pull_production_themes: always