Add NODE_ENV configuration for production cyf-hosting deployments #1727
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds instructions to set NODE_ENV=production for all Node.js applications to prevent resource exhaustion on the hosting infrastructure. Changes: - Added step-by-step guide for setting NODE_ENV environment variable - Includes screenshots for clarity - Applied to both backend and frontend deployment guides This configuration is now mandatory for all JavaScript/Node.js projects to ensure applications run in production mode rather than development mode.
👷 Deploy request for cyf-curriculum pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-piscine pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-common pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-sdc pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-itd pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-tracks pending review.Visit the deploys page to approve it
|
👷 Deploy request for cyf-launch pending review.Visit the deploys page to approve it
|
Member
illicitonion
left a comment
illicitonion
left a comment
There was a problem hiding this comment.
LGTM - a few small suggestions, thanks!
|
|
||
| ## Add NODE_ENV to Your Project | ||
|
|
||
| **Required for:** All JavaScript/Node.js projects (frontend and backend) |
Member
There was a problem hiding this comment.
Suggested change
| **Required for:** All JavaScript/Node.js projects (frontend and backend) | |
| **Required for:** All Node.js projects (anything that has a `package.json` file) |
Author
There was a problem hiding this comment.
update and change the code as you suggested
| 3. Fill in the form: | ||
| - **Name:** `NODE_ENV` | ||
| - **Value:** `{{team.NODE_ENV}}` | ||
| - Check **"Available at Runtime"** ✅ |
Member
There was a problem hiding this comment.
Suggested change
| - Check **"Available at Runtime"** ✅ | |
| - Make sure **"Available at Build time" is not checked** ❌ | |
| - Make sure **"Available at Runtime"** is checked ✅ |
|
|
||
| ## Add NODE_ENV to Your Project | ||
|
|
||
| **Required for:** All JavaScript/Node.js projects (frontend and backend) |
Member
There was a problem hiding this comment.
Suggested change
| **Required for:** All JavaScript/Node.js projects (frontend and backend) | |
| **Required for:** All Node.js projects (anything that has a `package.json` file) |
| 3. Fill in the form: | ||
| - **Name:** `NODE_ENV` | ||
| - **Value:** `{{team.NODE_ENV}}` | ||
| - Check **"Available at Runtime"** ✅ |
Member
There was a problem hiding this comment.
Suggested change
| - Check **"Available at Runtime"** ✅ | |
| - Make sure **"Available at Build time" is not checked** ❌ | |
| - Make sure **"Available at Runtime"** is checked ✅ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Adds step-by-step instructions for configuring NODE_ENV on all Node.js applications deployed to CYF Hosting.
Changes:
Why this is important:
This configuration is now mandatory for all JavaScript/Node.js projects deployed to CYF Hosting. Without NODE_ENV, applications run in development mode with file watching enabled, consuming ~100x more system resources per container. This inefficiency led to infrastructure failures on January 28, 2026, when file descriptors were exhausted across 150+ deployments. Setting NODE_ENV ensures applications run efficiently and maintains hosting stability for all users.
Common Content?
Common Theme?
Issue number: # Related to infrastructure incident on 2026-01-28
Org Content?
Guide | CYF Hosting | Deployment | Configuration
Checklist
Who needs to know about this?
@illicitonion