Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to declare plugin options (version, activate, etc.) in vvv-custom.yml ? #1935

looshi opened this issue Aug 31, 2019 · 5 comments · Fixed by Varying-Vagrant-Vagrants/


Copy link

looshi commented Aug 31, 2019

Is it possible to declare plugins and plugin options in vvv-custom.yml ?

I don't see any information about how to declare plugins in vvv-custom.yml in the vvv documentation here:

For example:

        - { plugin: "akismet", activate: true, etc. }  # Doesn't seem to work.
        - akismet  # Seems to work, but can't set any options 

Here is the full vvv-custom.yml that I am trying to use.

After editing I run vagrant reload --provision.

# IMPORTANT, if you change this file, you have to reprovision:
# `vagrant reload --provision` OR `vagrant up --provision`

    skip_provisioning: false
    description: "My Site"
      - my-site.test

      admin_user: admin
      admin_password: password
      title: My Site
      db_prefix: wp_
      multisite: false
      xipio: false
      version: 5.2.2
      locale: en_US
        - { plugin: "akismet", activate: true }
        - astra
      delete_default_plugins: true
      delete_default_themes: true

# Utilities
# are system level items that aren't websites, that install tools or packages
# the core utilities install tools such as phpmyadmin
  core: # The core VVV utility
    - tls-ca # HTTPS SSL/TLS certificates
    - phpmyadmin # Web based database client
    #- memcached-admin # Object cache management
    #- opcache-status # opcache management
    #- webgrind # PHP Debugging
    #- mongodb # needed for Tideways/XHGui
    #- tideways # PHP profiling tool, also installs xhgui check
    #- php56
    #- php70
    #- php71
    #- php72
    #- php73

# vm_config controls how Vagrant provisions the virtual machine, and can be used to
# increase the memory given to VVV and the number of CPU cores.
# It can also be used to override the default provider being used within Vagrant.

  # For WP core development we recommend at least 2GB ( 2048 ),
  # If you have 4GB of RAM, lower this to 768MB or you may encounter issues
  memory: 2048
  # CPU cores:
  cores: 2

  # this tells VVV to use the prebuilt box copied from the USB drive at contributor days
  # once set to false, do not change back to true, and reprovision
  # wordcamp_contributor_day_box: false

  # Due to a limitation within Vagrant, the specified provider is only respected on a clean `vagrant up`
  # as Vagrant currently restricts you to one provider per machine
  # provider: vmware_workstation

# General VVV options
  # Backup the databases to the database/backups subfolder on halt/suspend/destroy, set to false to disable
  db_backup: true
  # Import the databases if they're missing from backups
  db_restore: true
  # set to true to use a synced shared folder for MariaDB database storage
  db_share_type: false
  # GitHub token to use from composer
  #github_token: xxxxxx

After the vagrant provisioner has completed, if I visit the admin portion of the site no plugins are installed :

Screen Shot 2019-08-31 at 9 10 00 AM


Copy link

tomjn commented Aug 31, 2019 via email

Copy link

looshi commented Sep 1, 2019

@tomjn okay, thanks.

Copy link

Mte90 commented Sep 1, 2019

Check at
Right now is not possible to specify versions but only the plugin to install and activate

For when you just need a simple dev site. Contribute to Varying-Vagrant-Vagrants/custom-site-template development by creating an account on GitHub.

@Mte90 Mte90 self-assigned this Sep 20, 2019
Copy link

Mte90 commented Sep 20, 2019

I think that can I improve the docs after this suggestions :-)

Copy link

lock bot commented Feb 22, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

Successfully merging a pull request may close this issue.

3 participants