Skip to content

Conversation

@vcanales
Copy link
Member

I find myself having to stop my Gutenberg environment, which uses the default port, when working on both at around the same time. This change should make it easier to have both environments running in parallel.

I realize I could choose to run a .wp-env.override.json file as well, but I think this might benefit other folks as well.

I find myself having to stop my Gutenberg environment, which uses the
default port, when working on both at around the same time. This change
should make it easier to have both environments running in parallel.
@vcanales vcanales added enhancement New feature or request build tooling labels Apr 30, 2024
@vcanales vcanales changed the title Use non-default port for wp-env Proposal: Use non-default port for wp-env Apr 30, 2024
Copy link
Contributor

@matiasbenedetto matiasbenedetto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The containers run at the specified ports. It looks good to me.

@pbking pbking merged commit 0524255 into trunk May 9, 2024
@pbking pbking deleted the try/use-non-default-port-for-wp-env branch May 9, 2024 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build tooling enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants