You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In development environment, some cases me might need to run some additional backend services (cache, custom API…) along with nhost services (GraphQL , auth, storage).
I like to leverage same magicDNS benefits for custom services.
Ask
Please include some additional SNAs in the certs provisioned by nhost cli. E.g, *.app1.local.nhost.run , *.app2.local.nhost.run etc so we can access them via
Hello,
the issue is that format doesn't follow the format we use in the cloud but we should be able to do something like xdfp-192-168-1-123.svc.local.nhost.run, where xdfp is a short hash of the run service name.
Thanks. sound good, this solution will work for multiple local Run services.
You can also consider adding optional backend port: e.g., xdfp-192-168-1-123-8080.svc.local.nhost.run
In development environment, some cases me might need to run some additional backend services (cache, custom API…) along with nhost services (GraphQL , auth, storage).
I like to leverage same magicDNS benefits for custom services.
Ask
Please include some additional SNAs in the certs provisioned by nhost cli. E.g,
*.app1.local.nhost.run
,*.app2.local.nhost.run
etc so we can access them viahttps://local.app1.local.nhost.run/
https://local.app2.local.nhost.run/
Note
HTTPS is also needed to try some web Features (Web Crypto, Service Workers, Notifications) for local development
Tasks
The text was updated successfully, but these errors were encountered: