Closed benleeth closed 4 years ago
hosts parameter doesn't support as I know folder, hosts if only the host, for domains with folder is something that you need to do manually on creating a new site inside the multisite.
hosts parameter doesn't support as I know folder, hosts if only the host, for domains with folder is something that you need to do manually on creating a new site inside the multisite.
+1, these need to be hostnames, not URLs, e.g. domain names.
This is what it should be instead:
hosts:
- bonedry.test
The hosts section is used for Nginx and the hosts file, so subdirectories and files aren't relevant to this section
I'm getting the same error message when just having this provision too -
description: "Local install of cornerstoneautismcenter.com"
repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
nginx_upstream: php73
hosts:
- cornerstoneautismcenter.test
- cornerstoneautismfoundation.test
custom:
wp_type: subdomain
And the vvv-auto-cornerstone-autism-provision-48b8dd21037ebb245480d88f43cc4ed1.conf
file has server_name {vvv_hosts};
.
Just weird because they both worked fine until the updates I ran this morning.
I tried to reproduce using this:
cornerstone-autism:
description: "Local install of cornerstoneautismcenter.com"
repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
nginx_upstream: php73
hosts:
- cornerstoneautismcenter.test
- cornerstoneautismfoundation.test
custom:
wp_type: subdomain
Looking at the log for the provision gives:
* Configuring WordPress
WordPress is present but isn't installed to the database, checking for SQL dumps in wp-content/database.sql or the main backup folder.
* Installing WordPress Stable...
* Using multisite subdomain type install
Error: The site you have requested is not installed.
Run `wp core install` to create database tables.
[38;5;9m---------------------------------------------[0m
[38;5;9m! Site provisioner failed! Check the full log for more details[0m
[38;5;9m---------------------------------------------[0m
This implies the wp core multisite-install
failed, and so the provisioner script aborted before it could get to the Nginx config part
As a sidenote this:
utilities:
core:
- tls-ca
- phpmyadmin
- memcached-admin
- opcache-status
- webgrind
#- mongodb
#- tideways
- php56
- php70
- php72
- php73
- php74
can be replaced with this:
utilities:
core:
- tls-ca
- phpmyadmin
- memcached-admin
- opcache-status
- webgrind
- php
Thanks for the knowledge on everything, @tomjn and @Mte90 !! I have everything back up and running smoothly!! Just to let you know, I did have an error with:
install_plugins:
- simple-history
Said the directory already existed then failed out. Seemed a pretty extreme reason to abort but wanted to let you know. Again, thanks for the assistance!
I've been trying to debug why mine doesn't want to work, the core multisite-install step fails, though it succeeds if I manually run it. I've some adjustments to the site provisioner to try and improve things
A combination of #2023 and https://github.com/Varying-Vagrant-Vagrants/custom-site-template/pull/33 resolve the issue successfully here
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.
Updated the vagrant box and pulled the VVV repo for update this morning. Provisioning now fails with multiple hosts listed.
Expected Behavior
Normal VVV operations
Current Behavior
Receiving error "Job for nginx.service failed because the control process exited with error code." and VVV not working. Removing any and all subdirectory or subdomain multisites, things work correctly.
Possible Solution
I don't know what the solution is but I can see what is going wrong. Under normal provisioning of the
nginx.conf
file, it would be something likeserver_name vvv vvv.dev vvv.local vvv.localhost;
. But, thevvv-auto-bone-dry-provision-5044fd9a0ee0c5b29ca4f7d5c3b16d0a.conf
file hasserver_name {vvv_hosts};
.Your Environment
OS: OS X 10.15.1 VirtualBox: 6.0 VVV: 3.3.0-develop
Logs
provision:
config.yml file: