Feature Request: Add the ability for Studio to change the port number used by a specific WordPress installation.

[juanmaguitar]

What

Add to settings an option to specify the PORT where a specific WordPress site is served from

Why

Lately, I’ve been running into several conflicts between WordPress Studio sites and WordPress instances launched from Docker containers (via wp-env), mainly due to port collisions.

I’m not entirely sure how Studio assigns ports to each WordPress instance, but having the option to manually set a specific port would be extremely helpful to prevent these conflicts with other development environments.

How

No response

[wojtekn]

@juanmaguitar, do you experience this issue when using custom domains? Could you please share more detailed steps to reproduce the error you are getting when a port collision occurs?

[juanmaguitar]

do you experience this issue when using custom domains?

@wojtekn yes, I'm experiencing this issue with a site in WordPress Studio that uses a custom domain

Could you please share more detailed steps to reproduce the error

Here are the steps I'm taking to reproduce the error:

1. I launch a WordPress instance using Docker via wp-env

2. After that I activate one of my WordPress Studio sites that use a custom domain and I get the following error

3. These are the settings of the site that's giving me an error

Port 8888, which is causing the conflict, is a pretty common one—so it’s likely that other developers using various tools to set up a local WordPress development environment might run into the same issue.