1. Hi Erica!

    Great article! I was trying to figure this out and it’s actually kinda simple after reading your article 🙂

    I was wondering if you’ve also deployed websites using this methodology? Do you think it would it be possible to deploy multiple WordPress installations to a single VPS using this?


    • Hi Nick!

      Glad you enjoyed the article. 🙂

      I haven’t deployed any sites using Bedrock/Ansible yet, but I wouldn’t think there would be a major issue with deploying multiple sites the same as running them off your localhost. I’m hoping to play around with this on a Droplet soon, but if you come up with something and write about it let me know. I’m really digging how easy Bedrock/Ansible is to work with.


  2. Thanks Erika, this helped me get up and running.

    Two stumbles for me.
    1) When I first went into the `wordpress_sites.yml` file there wasn’t an env: section and it would seem it’s not needed for local.
    2) Related, one does need to also go into `vaults.yml` and add the site name there or `vagrant up` will fail.

    Those seem like things that maybe just changed in Trellis since you wrote this.

    Again, this post was super helpful in getting me up and running so thanks!

  3. Super helpful – thanks Erica!

    It hadn’t clicked that I could rename the default ‘site’ directory. It all makes so much more sense now 🙂

  4. Hey, Erica, nice article. By the way this multiple site setup would not work on Windows if you used NFS share with winnfsd (Error: mount.nfs: access denied by server etc.). Works perfectly well with just a single site install though.