-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
static port mapping for local development #560
Labels
enhancement
New feature or request
Comments
Just a note that this is implemented via an env var with http proxies. |
@davemooreuws is there an example? |
Hey @chimon2000, the http proxy one was done on the SDK level (for the node-sdk). I think the feature request might be looking for something more generic and broad in the nitric yaml like: @jyecusch ports:
main: 4001
private: 4002 |
Ah yes, that would be a very nice feature.
…On August 12, 2024, GitHub Notifications ***@***.***> wrote:
> @davemooreuws <https://github.com/davemooreuws> is there an example?
>
Hey @chimon2000 <https://github.com/chimon2000>, the http proxy one
was done on the SDK level (for the node-sdk).
<https://github.com/nitrictech/node-
sdk/blob/6bc461c399c17177f9ce0c0454e0adfd40d292ed/src/resources/http.ts#L111>
I think the feature request might be looking for something more
generic and broad in the nitric yaml like: @jyecusch
<https://github.com/jyecusch>
ports: main: 4001 private: 4002
|
Finished, example config # local.nitric.yaml
# Local development configuration for Nitric services.
apis:
# API Resources
first-api:
port: 6001
second-api:
port: 6002
my-db-api:
port: 6003
my-secret-api:
port: 6004
websockets:
# WebSocket Resources
socket:
port: 7001
socket-2:
port: 7002
socket-3:
port: 7002 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Suggestion
Allow for API and other entrypoint ports to be set to static values based on the resource's name.
Value
Allow local development which includes automated tests or UIs that interact with the APIs to be configured once, avoiding port changes when new APIs are added to existing projects.
The text was updated successfully, but these errors were encountered: