Question

Access to internal service at build-time

Hey Folks,

I’m using DO App-Platform with two Node.JS-Components.

One component is intended to run as a kind of “proxy” and can only be accessed internal.

The other component is public and when building, it connects to the “proxy” to get some “information”.

But somehow the public-component is not able to resolve the internal hostname/component-name of the “proxy” when building. Is this “working as intended”?

For me it looks like the components do not have access to each other when building.

Or am I doing something wrong?


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

👋🏼 @hermsi1337

Yes, this is correct. Routing between components is only available at run time. It is not possible to communicate between components or run services at build time.

Can you please expand a bit on your need for this in case we can find a different way to achieve this?