By Dennis
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?
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!
👋🏼 @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?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.