reverse proxy support for local development

[galki]

nx is about shared code and multiple apps. that means that for example, ports in development usually translate to subdomains in production. with some solutions (firebase) requiring ssl during development as well, a built-in, local certificate-generating reverse proxy may be considered a popular and helpful feature.

[galki]

the way i currently do it on xplat (to be clear xplat doesn't come with this feature) is with these scripts:

"generate.proxy.cert": "node proxy/cert/generate",
"proxy": "node proxy/proxy",
"start.web.app": "ng serve web-app --host mydomain.localhost --port=4200"
"start.web.app2": "ng serve web-app --host subdomain.mydomain.localhost --port=4201"

1. generate.proxy.cert generates an ssl cert for proxy for mydomain.localhost (optional)
2. proxy reads package.json and extracts the hosts and ports of all apps to create a reverse-proxy with http-proxy

im using firebase functions for the backend so i hard code *.mydomain.localhost/api/ to redirect to localhost:5000/mydomain/us-central1/api (an express app firebase function served locally). per-app backend functionality can also be added.

using the --host flag doesnt interfere with default serving but seems to be required for reverse-proxy serving.

[galki]

used this chance to learn a bit about schematics: https://github.com/unitedhubs/reverse-proxy-schematic although not even sure how to exec the schematic after npm i -D reverse-proxy-schematic

[FrozenPandaz]

Hi, sorry about this.

This was mislabeled as stale. We are testing ways to mark not reproducible issues as stale so that we can focus on actionable items but our initial experiment was too broad and unintentionally labeled this issue as stale.

[github-actions]

This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.