Subsite URL not accessible from inside vagrant box

[danielck]

I was trying to write tests for a fairly complex multisite installation. As @ottok suggested to me, I could use wp-cli commands within the test script to get the correct URL for a specific subsite ID. This works, but then I discovered the subsites URL's are not accessible from within the vagrant box. Is there a trick to this or have I discovered a bug?

[ottok]

Related issue: Seravo/wp-palvelu-vagrant#37 "wp-pull-production-db fails for WP Network sites"

[ottok]

The latest Vagrant box released on Monday has an improved wp-pull-production-db command that now handles the main site of a network. Subdomains in a subdomain network cannot yet be automated however. See https://seravo.com/docs/get-started/release-notes/ and https://seravo.com/docs/configuration/wordpress-network/#local-development-with-vagrant-and-wordpress-network

[ottok]

The issue #81 is a duplicate of this. Subdirectory Networks run on Vagrant (and Docker) easily, but subdomain Networks would need custom domain mapping and search-replaces, which currently are not feasible to automate.

Currently one can use https://seravo.com/docs/configuration/wordpress-network/#wordpress-network-subdomain-installation + some custom wp-cli scripts to do the search-replace. We could still improve docs here and offer more examples of vagrant-up-customizer.sh