VVV: Q: `custom:` list of parameters in config.yml does not produce results
Hi,
I added a new website to my config.yml and needed to specify a bunch of custom parameters I got from the GitHub page for the custom site template. The config.yml snippet and vagrant status are pasted below.
Notes:
- I’ve commented out the problematic lines.
- The order of all parameters is preserved from the original file.
- Spaces and text formatting is as expected from a yaml file.
Thanks!
config.yml snippet
coolsite:
description: "Website description."
skip_provisioning: false
repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
php: 8.0
custom: # All custom properties at: https://github.com/Varying-Vagrant-Vagrants/custom-site-template
wp_type: none
delete_default_plugins: true
locale: bg_BG
install_plugins:
- wps-hide-login
- query-monitor
# wpconfig_constants: <!-- these do not work START
# WP_DEBUG: true
# WP_DEBUG_LOG: true
# WP_DISABLE_FATAL_ERROR_HANDLER: true
# FORCE_SSL_ADMIN: true
# WP_AUTO_UPDATE_CORE: minor
# TABLE_PREFIX: uoia_
#db_prefix: uoia_
#admin_user: wordmin <!-- these do not work END
wp_version: 5.8.10
hosts:
- coolsite.test
vagrant status output
__ __ __ __
\ V\ V\ V / v3.13.1 Ruby:3.3.6, Path:"/home/himynameis/vvv-local"
\_/\_/\_/ git::stable(f3ef893a)
Platform: linux shell:/bin/bash systemd vagrant-goodhosts CaseSensitiveFS shared_db_folder_disabled
Vagrant: v2.4.3, virtualbox: v7.0.20
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (11 by maintainers)
The provisioners get logged to files in the log folder that have more output than the terminal does, as long as you don’t mind all the colour codes still there