I have been at this for two days now and I’m at the end of the rope now. I’m not sure how to explain this very well but I will try. This sounds more like a DNS issue than a Trellis issue but I don’t know where to go from here… here’s what’s going on, I hope someone can help.
I have setup a local multisite trellis/bedrock environment and it works perfectly.
I have setup the staging group_vars and committed files to github successfully.
I have run ansible playbook and successfully provision the server on Digital Ocean with zero errors.
I have deployed the site files to the digital Ocean droplet as well with zero errors.
The domain is with Godaddy and I have changed the name servers to point to Digital Oceans.
It would be less confusing if for new multisite deploys the default WP install screen would show in the browser like it does for regular sites (non-multisite).
Trellis figures people will vary in how they want to install WP (manual in browser, manual via wp-cli, some script, etc.), so it leaves the install in your hands. I suspect it would be valuable if Trellis had a pre-built install-on-deploy option (disabled-by-default).