Import 'nodejs' repo

Author: rvedotrc

legacy/nodejs/README.md

@@ -1,3 +1,52 @@
-# nodejs
+# NodeJS - Fullstack development
 
-TODO
+For almost any web application, it is essential to have a backend. The backend is a place where we, the developers, can store our data, communicate with users and let the users communicate with us, do smart things like calculations, data processing etc.
+
+There are many languages for this. We might've heard of Java, C, C++, Go, Python, Ruby, PHP and the list goes on.
+There are two reasons why we at HYF choose Node.JS over others:
+
+1. You already know JavaScript, so it's easier to get started than other languages
+2. Node.js is great for making web APIs because it is asynchronous by nature and thus allows for high input/output. By this we mean that it allows many users to make very light requests at the same time.
+
+In this 3-week module, we will use NodeJS to create and connect both the backend api and serve the frontend html, css and javascript.
+Most of this course will focus on the backend part. Meaning building a webserver that has an api connected to a database.
+
+`Database <--> Webserver`
+
+## Planning
+
+| Week | Topic                                           | Preparation                         | Homework                             | Lesson plan                         |
+| ---- | ----------------------------------------------- | ----------------------------------- | ------------------------------------ | ----------------------------------- |
+| 1.   | HTTP; Introduction to node js; Simple webserver | [Preparation](week1/preparation.md) | [Homework](week1/homework/readme.md) | [Lesson plan](week1/lesson-plan.md) |
+| 2.   | Express                                         | [Preparation](week2/preparation.md) | [Homework](week2/homework/readme.md) | [Lesson plan](week2/lesson-plan.md) |
+| 3.   | Database connection; API                        | [Preparation](week3/preparation.md) | [Homework](week3/homework/readme.md) | [Lesson plan](week3/lesson-plan.md) |
+
+## Pre-requisites
+
+We will build on knowledge from the following HYF (sub)modules. If we feel we have gaps we should review the curriculum ourselves or ask a teacher to help.
+
+- [JavaScript](https://github.com/HackYourFuture-CPH/JavaScript)
+- [Git](https://github.com/HackYourFuture-CPH/git)
+- [CommandLine](https://github.com/HackYourFuture-CPH/CommandLine)
+
+## What will we learn?
+
+- What is Node.js?
+- Using Node Package Manager (NPM)
+- Using `import` to include modules
+- Using `express` to make a RESTful API
+- Using `mysql` to connect the API to the backend
+- Postman
+
+## Extra practice
+
+If you have the time, you could follow another simple set of exercises to get a better grasp of Node.js and some more practice.
+Feel free to bring any questions from this to the class or raise them on slack!
+
+Clone the repository that holds the exercises templates: <https://github.com/HackYourFuture-CPH/Nodejs-exercise-template.git>
+
+See each week's `readme.md` and follow the instructions to setup the server.
+
+---
+
+_Please help us improve and share your feedback! If you find better tutorials or links, please share them by opening a Pull Request._

legacy/nodejs/assets/deploy-step-1.PNG

@@ -0,0 +1,71 @@
+# Server
+
+Create a new, separate folder somewhere on your machine:
+
+```shell
+mkdir nodejs-week1
+code nodejs-week1 # to open the folder in VS Code
+```
+
+You can also reuse some other folder. Main thing to watch out for is that the folder you decide to use should ideally be empty.
+
+---
+
+Initialize and install:
+
+```shell
+npm init -y
+npm pkg set type="module"
+npm install express
+echo node_modules/ >> .gitignore
+```
+
+Make sure you see a `package.json`.
+Make sure you have `"type": "module"` in your `package.json`.
+Do you see `express` somewhere in `package.json`?
+Make sure you see the `node_modules` folder.
+Also make sure that the `node_modules/` folder is ignored by Git.
+
+---
+
+Create a file called `app.js`:
+
+```js
+import express from "express";
+const app = express();
+const port = 3000;
+
+app.get("/", (req, res) => {
+  res.send("Hello Class!");
+});
+
+app.listen(port, () => {
+  console.log(`Listening on port ${port}`);
+});
+```
+
+Start your server!
+
+```shell
+node app.js
+```
+
+Go to <http://localhost:3000> in your browser to verify that everything is working as expected.
+
+Press Ctrl-C to shut down the server.
+
+---
+
+**Task:**
+
+- Add a `/info` route to `app.js`.
+- It should respond with a **JSON object** containing the Node.js version; something like this: `{ "nodeVersion": "v17.3.0" }`
+- You can get the Node.js version from `process.version`
+
+To test that the response is indeed JSON, you can use Postman or cURL:
+
+```shell
+curl -i localhost:3000/info
+```
+
+The response `Content-Type` header should look like this: `Content-Type: application/json; charset=utf-8`.

legacy/nodejs/assets/deploy-step-2.PNG

@@ -0,0 +1,48 @@
+# Database
+
+Now we want to connect to a MySQL database from Node.js.
+
+First we need to install some packages:
+
+```shell
+npm install mysql2 knex
+```
+
+---
+
+Create a new MySQL database named `hyf_node_week1`.
+In `app.js` we can now establish the database connection.
+Add the following to the top of `app.js`:
+
+```js
+import knex from "knex";
+const knexInstance = knex({
+  client: "mysql2",
+  connection: {
+    host: "127.0.0.1",
+    port: 3306,
+    user: "your_database_user",
+    password: "your_database_password",
+    database: "hyf_node_week1",
+  },
+});
+
+// The code from before is down here
+// [...]
+```
+
+---
+
+Using `knex.raw` we can now execute SQL queries.
+Let's extend the `/info` route to also respond with the MySQL version: `{ "nodeVersion":"v17.3.0", "mysqlVersion":"8.0.30" }`
+
+```js
+app.get("/info", async (req, res) => {
+  const [rows] = await knexInstance.raw("SELECT VERSION()");
+
+  res.json({
+    nodeVersion: process.version,
+    mysqlVersion: rows[0]["VERSION()"],
+  });
+});
+```

legacy/nodejs/assets/deploy-step-3.PNG

@@ -0,0 +1,63 @@
+# User routes
+
+## Note on server restarts
+
+It is annoying to shutdown the server with Ctrl-C and start it again every time you make a change and want to test the change:
+
+```shell
+npm install --save-dev nodemon
+```
+
+Also, it is recommended to add a script to `package.json`, like so:
+
+```json
+"scripts": {
+  "dev": "nodemon app.js"
+}
+```
+
+There is a command to do that:
+
+```shell
+npm pkg set scripts.dev="nodemon app.js"
+```
+
+Now you can run
+
+```shell
+npm run dev
+```
+
+to start a server that automatically restarts when you make changes 🎉
+
+## Schema
+
+Create a `users` table with the following fields:
+
+- `id` (primary key)
+- `created_at`
+- `confirmed_at` (can be `NULL`)
+- `first_name`
+- `last_name`
+- `email` (unique)
+
+## Routes
+
+- `/all-users` should respond with all users sorted by ID
+- `/unconfirmed-users` should respond with unconfirmed users
+- `/gmail-users` should respond with users with an @gmail.com email
+- `/2022-users` should respond with users created in 2022
+
+---
+
+## More routes
+
+- `/user-count` should respond with the number of users
+- `/last-name-count` should respond with how many users there are with a given last name, sorted alphabetically
+- `/first-user` should respond with the first user. If there are no users in the table, respond with a 404
+
+## Frontend <-> Backend integration
+
+Turn the `/` route into a HTML page that fetches the count value from `/user-count` and shows it. Feel free to style this in whatever way you see fit.
+
+Optional: update the count every 2 seconds or something like that.