content relocation

Author: gambitier

session 5/chapters/1. Hello Nodejs World.md

@@ -48,21 +48,3 @@ server.listen(port, () => {
 	console.log(`Server running on http://localhost:${port}/`);
 });
 ```
-
-# Purpose of Environment Variables
-
-[ref](https://www.section.io/engineering-education/nodejs-environment-variables/)
-
-Environment Variables are important to a software developer for multiple reasons.
-
-1. Separation of Concerns
-
-   Separation of Concerns refers to a software design principle that states that computer programs should be divided into distinct sections, such that each section addresses a separate concern.
-
-   Application Configuration is a section of the code that should be decoupled from the application. Good software practices state that app config requires strict separation of config from code. Such config files can be stored as environment variables.
-
-2. Protecting Config Keys
-
-   With the increasing popularity of cloud computing, more applications are using cloud services and other external APIs. Most of these come with config keys for control and access management. If the API keys are added to the application, and the code is pushed to a public repository on GitHub, this could lead to an unmonitored access problem. Unknown parties might end up using your API keys, leading to an unintended bill for your cloud services, and other potential security issues.
-
-   To solve this problem, the config keys can be added as environment variables and invoked from a closed environment from where the application is deployed.

session 5/chapters/3. Environment Variables in Nodejs.md

@@ -1,8 +1,8 @@
 # Environment Variables in Node.js
 
-In Node.js, process.env is a global variable that is injected during runtime. It is a view of the state of the system environment variables. When we set an environment variable, it is loaded into process.env during runtime and can later be accessed.
+In Node.js, `process.env` is a global variable that is injected during runtime. It is a view of the state of the system environment variables. When we set an environment variable, it is loaded into `process.env` during runtime and can later be accessed.
 
-dotenv is a module available on npm to load environment variables into process.env. dotenv can be added to your Node.js project by installing it from npm or yarn:
+`dotenv` is a module available on npm to load environment variables into process.env. dotenv can be added to your Node.js project by installing it from npm or yarn:
 
 ```
 # with npm
@@ -34,3 +34,21 @@ DB_PASS=password
 ```
 
 We can add this .env file to .gitignore so that our credentials are protected.
+
+# Purpose of Environment Variables
+
+[ref](https://www.section.io/engineering-education/nodejs-environment-variables/)
+
+Environment Variables are important to a software developer for multiple reasons.
+
+1. Separation of Concerns
+
+   Separation of Concerns refers to a software design principle that states that computer programs should be divided into distinct sections, such that each section addresses a separate concern.
+
+   Application Configuration is a section of the code that should be decoupled from the application. Good software practices state that app config requires strict separation of config from code. Such config files can be stored as environment variables.
+
+2. Protecting Config Keys
+
+   With the increasing popularity of cloud computing, more applications are using cloud services and other external APIs. Most of these come with config keys for control and access management. If the API keys are added to the application, and the code is pushed to a public repository on GitHub, this could lead to an unmonitored access problem. Unknown parties might end up using your API keys, leading to an unintended bill for your cloud services, and other potential security issues.
+
+   To solve this problem, the config keys can be added as environment variables and invoked from a closed environment from where the application is deployed.