Skip to content

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

Description

@looshi

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: https://varyingvagrantvagrants.org/docs/en-US/vvv-config/.

For example:

      plugins:
        - { plugin: "akismet", activate: true, etc. }  # Doesn't seem to work.
      plugins:
        - 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.

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

sites:
  my-site:
    skip_provisioning: false
    description: "My Site"
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - my-site.test

    custom:
      admin_user: admin
      admin_password: password
      admin_email: example@gmail.com
      title: My Site
      db_prefix: wp_
      multisite: false
      xipio: false
      version: 5.2.2
      locale: en_US
      plugins:
        - { plugin: "akismet", activate: true }
      themes:
        - astra
      delete_default_plugins: true
      delete_default_themes: true

# Utilities https://varyingvagrantvagrants.org/docs/en-US/utilities/
# are system level items that aren't websites, that install tools or packages
# the core utilities install tools such as phpmyadmin
utilities:
  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 https://varyingvagrantvagrants.org/docs/en-US/references/tideways-xhgui/
    #- 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.

vm_config:
  # 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
  # https://www.vagrantup.com/docs/providers/basic_usage.html#vagrant-up
  # provider: vmware_workstation

# General VVV options
general:
  # 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

thanks!

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions