- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 247 for porta (0.06 sec)
-
docs/pt/docs/advanced/behind-a-proxy.md
[entryPoints.http] address = ":9999" [providers] [providers.file] filename = "routes.toml" ``` Isso diz ao Traefik para escutar na porta 9999 e usar outro arquivo `routes.toml`. /// tip | "Dica" Estamos usando a porta 9999 em vez da porta padrão HTTP 80 para que você não precise executá-lo com privilégios de administrador (`sudo`). /// Agora crie esse outro arquivo `routes.toml`:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 15:28:18 UTC 2024 - 12.2K bytes - Viewed (0) -
docs/pt/docs/deployment/concepts.md
### Processos do Trabalhador e Portas Lembra da documentação [Sobre HTTPS](https.md){.internal-link target=_blank} que diz que apenas um processo pode escutar em uma combinação de porta e endereço IP em um servidor? Isso ainda é verdade.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Fri Oct 04 11:04:50 UTC 2024 - 19.7K bytes - Viewed (0) -
docs/pt/docs/contributing.md
$ uvicorn tutorial001:app --reload <span style="color: green;">INFO</span>: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ``` </div> como Uvicorn utiliza por padrão a porta `8000`, a documentação na porta `8008` não dará conflito. ### Traduções Ajuda com traduções É MUITO apreciada! E essa tarefa não pode ser concluída sem a ajuda da comunidade. 🌎 🚀
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 14.8K bytes - Viewed (0) -
docs/pt/docs/deployment/docker.md
RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt COPY ./app /code/app CMD ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "80"] # If running behind a proxy like Nginx or Traefik add --proxy-headers # CMD ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "80", "--proxy-headers"] ``` </details> ## O que é um Contêiner
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Aug 12 21:47:53 UTC 2024 - 37.4K bytes - Viewed (0) -
common-protos/k8s.io/api/networking/v1/generated.proto
// +optional optional k8s.io.apimachinery.pkg.util.intstr.IntOrString port = 2; // endPort indicates that the range of ports from port to endPort if set, inclusive, // should be allowed by the policy. This field cannot be defined if the port field // is not defined or if the port field is defined as a named (string) port.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 25.2K bytes - Viewed (0) -
istioctl/pkg/describe/describe_test.go
}, { port: corev1.ServicePort{ AppProtocol: &http, Protocol: corev1.ProtocolTCP, }, expectedProtocol: "HTTP", }, { port: corev1.ServicePort{ Protocol: corev1.ProtocolTCP, Port: 80, }, expectedProtocol: "auto-detect", }, { port: corev1.ServicePort{ Protocol: corev1.ProtocolUDP, Port: 80, },
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Aug 01 20:04:20 UTC 2024 - 30.8K bytes - Viewed (0) -
istioctl/pkg/writer/ztunnel/configdump/testdata/dump.json
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Tue Apr 16 03:28:36 UTC 2024 - 33.1K bytes - Viewed (0) -
cni/pkg/plugin/sidecar_redirect.go
} func validatePortList(ports string) error { if _, err := parsePorts(ports); err != nil { return fmt.Errorf("portList %q invalid: %v", ports, err) } return nil } func validatePortListWithWildcard(ports string) error { if ports != "*" { return validatePortList(ports) } return nil } // validateCIDRListWithWildcard validates the includeIPRanges parameter
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Jan 26 20:34:28 UTC 2024 - 10.6K bytes - Viewed (0) -
istioctl/pkg/validate/validate_test.go
kind: Service metadata: name: hello spec: ports: - name: http port: 9080` validPortNamingWithSuffixSvc = ` apiVersion: v1 kind: Service metadata: name: hello spec: ports: - name: http-hello port: 9080` invalidPortNamingSvc = ` apiVersion: v1 kind: Service metadata: name: hello spec: ports: - name: hello port: 9080`
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 02 16:18:14 UTC 2024 - 21.4K bytes - Viewed (0) -
common-protos/k8s.io/api/networking/v1beta1/generated.proto
// IngressPortStatus represents the error condition of a service port message IngressPortStatus { // port is the port number of the ingress port. optional int32 port = 1; // protocol is the protocol of the ingress port. // The supported values are: "TCP", "UDP", "SCTP" optional string protocol = 2; // error is to record the problem with the service port // The format of the error shall comply with the following rules:
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 14.9K bytes - Viewed (0)