Bedrock multisite with different domains + local dev procedure & deploy

@trainoasis I don’t use Valet… been wanting to check that out though, just haven’t had a chance.

I’m on windows so I use WSL, their built in linux kernal, and it all worked locally for me, but I’m not trying to do https locally.

  1. & 2. both sound like valet issue. but I’d double check and make sure you’ve got that https in the network site settings.

  2. Correct, this just relates to your A DNS records, it won’t affect your MX records at all.

  3. Yep :+1:

  4. Since I’m running on Windows, Trellis is not something I use. I’m tried it before, but its just too slow for me on Windows. I’m not sure if it was an issue with my machine or not but I just prefer the WSL route. That said WSL2 is coming out soon and will be much more compatible with Trellis, so I might give it a go soon.

But to answer your question on how to manage stages, bedrock is perfect for this. I used to use capistrano that works great with bedrock… but I don’t really use ruby and capistrano was the only reason I had it installed. One day, it broke on me (a windows thing I think?), so I went looking for deployment alternatives and discovered a php alternative to capistrano called Deployer. Looks like there is a thread on here for how to set it up with Bedrock, I kind of stumbled my way through it so I won’t try to explain my setup as its probably not the best way to do it.

So for multiple stages, I use bedrock’s normal .env to handle config per server and deployer to push my files to each stage as needed. You’d be able to deploy any branch to your staging server for testing features and what not. As far as multisite + handling stages, I might have to do a little config per server/stage, but once its setup its usually good to go.

Let me know if you run into any issues, maybe I can help!