This repository was archived by the owner on Apr 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 518
Setting node's NODE_ENV based off of ASPNETCORE_ENVIRONMENT? #230
Comments
NODE_ENV
based off of ASPNETCORE_ENVIRONMENT
?
Yes, this sounds good! If you want to do a PR that would be great, otherwise I'll get to this within the next couple of weeks. |
SteveSandersonMS
added a commit
that referenced
this issue
Aug 16, 2016
…us auto-populate NODE_ENV based on IHostingEnvironment when possible. Fixes #230
Now implemented. I'll publish updated packages soon. I've also added an If you just want |
geirsagberg
added a commit
to geirsagberg/JavaScriptServices
that referenced
this issue
Aug 17, 2016
* upstream/dev: Add ability to configure environment variables for Node instances, plus auto-populate NODE_ENV based on IHostingEnvironment when possible. Fixes aspnet#230 Rename PrimeCache to PrimeCacheAsync (keeping older name as obsolete overload). Fixes aspnet#246. Prerenderer now passes original (unescaped) URL to Node - fixes aspnet#250 In WebpackDevMiddleware, allow configuration of ProjectPath (implements aspnet#262)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Or, allow us to manually specific environment variables for the node instances ourselves.
The text was updated successfully, but these errors were encountered: