Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I need to direct all traffic through an Nginx service component for reverse proxying, routing, rate limiting, etc.
The app runs without error on my local dev environment via Docker-Compose.
I try to update my App Platform app’s app spec from the terminal via doctl apps update <app-id>, but I get back an error: 400 (request "2887fea5-dc3a-40d2-a370-83659aa5f651") errors validating app spec; first error in field "ingress.rules.rule.match.path.prefix": rule match path prefix "/" already in use by rule with component: "nginx".
What’s strange is that even if I comment out every ingress rule in the app spec, the error still occurs.
I’m not sure about how I’m messing up. Any help is appreciated.
Note: I already have a version of my app currently running on App Platform. I’m not sure if somehow an ingress rule in the currently-running app’s app spec is causing the error.
nginx service component will handle routing to the client service component, and the api service component.ingress:
rules:
- match:
path:
prefix: /
component:
name: nginx
preserve_path_prefix: true
- match:
path:
prefix: /ws
component:
name: nginx
preserve_path_prefix: true
- match:
path:
prefix: /api
component:
name: nginx
preserve_path_prefix: true
services:
- name: nginx
...
- name: client
...
- name: api
...
Stefan
Ianalytics Corporation S.A.C. (RUC: 20605079947)
3630316526124b4190e628cd69be1e
a6309a057c3f4cb38fb2e7feb67236
KFSys
a0aa4c11068a4e98bc3cde06ce6c8c
Kailey Ketchum
Matteo Scarpa
Matteo Scarpa
fullammo
1a3ca91ed97c49039b3e74fb7229fa
jamshed.latipov