The current setup uses NGINX as a proxy, allowing only HTTPS access via subdomains. To increase flexibility and adaptability for different environments, add the following flags to the deploy command:
--no-tls: Disables TLS for all services, allowing access via HTTP or gRPC without encryption.--port-routing: Enables access to services by specific ports instead of subdomains.
These options will make it easier to deploy services in internal or local environments.
Example Usage:
-
Default Setup (TLS with Subdomains):
Keeps the existing behavior with HTTPS access over subdomains.
-
Non-TLS HTTP and gRPC Access:
Enables HTTP and gRPC without TLS, with subdomain routing.
-
Port-Based Routing Without TLS:
deploy --no-tls --port-routing
Configures services to allow HTTP and gRPC without TLS, with each service accessible on a specified port.
-
Port-Based Routing with TLS:
Uses HTTPS but routes services via ports instead of subdomains.
The current setup uses NGINX as a proxy, allowing only HTTPS access via subdomains. To increase flexibility and adaptability for different environments, add the following flags to the
deploycommand:--no-tls: Disables TLS for all services, allowing access via HTTP or gRPC without encryption.--port-routing: Enables access to services by specific ports instead of subdomains.These options will make it easier to deploy services in internal or local environments.
Example Usage:
Default Setup (TLS with Subdomains):
Keeps the existing behavior with HTTPS access over subdomains.
Non-TLS HTTP and gRPC Access:
Enables HTTP and gRPC without TLS, with subdomain routing.
Port-Based Routing Without TLS:
Configures services to allow HTTP and gRPC without TLS, with each service accessible on a specified port.
Port-Based Routing with TLS:
Uses HTTPS but routes services via ports instead of subdomains.