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.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @larryryan0824,
I can’t say I’ve actually had similar Apps being built so it’s just a short in the dark for me however, I’ve searched around DigitalOcean’s community, docs and tutorials and found those 2, hope they can be of some help until someone else answers this :
https://www.digitalocean.com/community/tutorials/angular-socket-io
Hope this helps!
I’m not sure if this is what’s causing the error, but just in case it helps:
made the server as component of it with its path at /api. I have configured socket.io to use that path and know it is correct due to the url returning that error code.
By default, if a component is configured with an HTTP route, the app/code will see incoming requests without the /api prefix. For example, a request coming in to /api/login will be rewritten to /login before being forwarded to the app.
If this is not the desired behavior, you can instruct App Platform to keep the prefix by following these steps:
preserve_path_prefix option to true...
services:
- name: api
routes:
- path: /api
preserve_path_prefix: true
...
For more info on the app spec, please see the reference.