self-contained deployment with node #1092

New Issue

fergalmoran · 2025-08-09T17:18:50Z

fergalmoran commented

2025-08-09 17:18:50 +00:00

Originally created by @emailtowalter on 1/25/2017

We use cloud foundry ( on Linux) to run .net core. The way we deploy is to publish the website as a self-contained package.

Here is the issue: Node.js is not on the platform, and we do not want to install it on the platform either. A ideal case would be to include node.js as part of the deployment package during publishing process. Of cause, it has to be the right node.js runtime depending on the OS.

At this moment, we have a workaround : include the node and npm from linux platform in the root directory. But it is not elegant.

Thanks,

Walter

*Originally created by @emailtowalter on 1/25/2017* We use cloud foundry ( on Linux) to run .net core. The way we deploy is to publish the website as a self-contained package. Here is the issue: Node.js is not on the platform, and we do not want to install it on the platform either. A ideal case would be to include node.js as part of the deployment package during publishing process. Of cause, it has to be the right node.js runtime depending on the OS. At this moment, we have a workaround : include the node and npm from linux platform in the root directory. But it is not elegant. Thanks, Walter

fergalmoran closed this issue

2025-08-09 17:18:50 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1092