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

feat: TLS for Nhost Run services #914

Open
xmlking opened this issue Sep 14, 2024 · 2 comments
Open

feat: TLS for Nhost Run services #914

xmlking opened this issue Sep 14, 2024 · 2 comments
Assignees

Comments

@xmlking
Copy link

xmlking commented Sep 14, 2024

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

https://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

@dbarrosop
Copy link
Member

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.

@dbarrosop dbarrosop self-assigned this Sep 16, 2024
@xmlking
Copy link
Author

xmlking commented Sep 16, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants