Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change forceSamePort parameter to also be a config option #816

Closed
hasezoey opened this issue Oct 18, 2023 · 2 comments · Fixed by nodeshift/mern-workshop#229
Closed

Change forceSamePort parameter to also be a config option #816

hasezoey opened this issue Oct 18, 2023 · 2 comments · Fixed by nodeshift/mern-workshop#229
Labels
enhancement released on @beta released Pull Request released | Issue is fixed
Milestone

Comments

@hasezoey
Copy link
Member

Currently forceSamePort can only be set via the MongoMemoryServer.start parameter, and is currently unavailable for .create or replsets, this issue tracks to add some kind of option to InstanceOpts to force the same port.

Note about semantics:
it will work the same as forceSamePort, where the parameter takes priority. if set to true and port is defined, it will not generate a port, port is undefined, it will generate a port regardless.

Copy link

🎉 This issue has been resolved in version 10.0.0-beta.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@hasezoey hasezoey added this to the 10.0 milestone Jul 15, 2024
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement released on @beta released Pull Request released | Issue is fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant