🔄 Update "How to deploy a Node.js application with Docker" (#1236)

Author: matteocontrini

tutorials/deploy-nodejs-with-docker/01.en.md

@@ -2,7 +2,7 @@
 SPDX-License-Identifier: MIT
 path: "/tutorials/deploy-nodejs-with-docker"
 slug: "deploy-nodejs-with-docker"
-date: "2024-09-05"
+date: "2025-09-02"
 title: "How to deploy a Node.js application with Docker"
 short_description: "Learn how to deploy a Node.js app to an Ubuntu server with Docker, Docker Hub and Docker Compose"
 tags: ["Docker", "Deploy", "Cloud", "Lang:JS"]
@@ -45,13 +45,11 @@ This tutorial shows how to deploy a Node.js application to a cloud server throug
   * <kbd>package.json</kbd>
     ```json
     {
-        "version": "1.1.0",
+        "version": "1.0.0",
+        "private": true,
         "name": "myproject",
-        "description": "Example package.json file.",
-        "main": "src/index.js",
-        "scripts": {
-           "build": "echo \"Building the application\""
-        }
+        "description": "Example project",
+        "main": "src/index.js"
     }
     ```
 
@@ -87,7 +85,7 @@ In case you're just getting started with Docker, here are some terms that are wo
 Create a file called `Dockerfile` with the following content in the root of your Node.js project directory:
 
 ```do
-FROM node:20.17
+FROM node:22
 
 ENV NODE_ENV=production
 
@@ -106,7 +104,7 @@ CMD [ "node", "src/index.js" ]
 
 The `Dockerfile` is the place where you put the instructions that allow Docker to *build* an image. Every instruction represents the creation of a layer, which is a modification of the image file system that is being created.
 
-In this case, we're composing our image by starting from a template, sometimes called the *base image*, that in this case is `node:20.17`. This is an official image provided by the Docker company, and you can find more about it [here](https://hub.docker.com/_/node).
+In this case, we're composing our image by starting from a template, sometimes called the *base image*, that in this case is `node:22`. This is an official image provided by the Docker company, and you can find more about it [here](https://hub.docker.com/_/node).
 
 The next step sets the `NODE_ENV` environment variable to `production`. The main effect here is to avoid installing development packages when running the npm installation below, but it can often lead to better optimizations in modules you might be relying on.
 
@@ -148,7 +146,7 @@ docker build -t myproject .
 
 The `-t` option specifies the name of the image, in this case `myproject`. The `.` at the end of the line is required to tell Docker to look for a `Dockerfile` in the current directory.
 
-**NOTE**: the first time that you run the build, it will take a while because Docker has to download all the layers of the base image (Node.js 20.17 in this case).
+**NOTE**: the first time that you run the build, it will take a while because Docker has to download all the layers of the base image (Node.js 22 in this case).
 
 Since we're going to upload this image to the Docker Hub online registry (to make it accessible from our server), we need to name the image by using a specific convention.
 
@@ -163,10 +161,10 @@ Where `username` is your Docker Hub username, and `latest` is the *tag* of the i
 ```sh
 docker build -t myproject .
 docker tag myproject username/myproject:latest
-docker tag myproject username/myproject:20240905
+docker tag myproject username/myproject:20250902
 ```
 
-These commands build an image and then tag it with the tags `latest` and `20240904` (the date this tutorial was last updated).
+These commands build an image and then tag it with the tags `latest` and `20250902` (the date this tutorial was last updated).
 
 Docker Hub doesn't remove old images by default, so this allows to have an history of all the images that you pushed to the registry. The image with tag `latest` will always be the one that was most recently built, while the older ones will be tagged with a date.
 
@@ -257,7 +255,7 @@ This is a very basic Docker Compose file that configures a single container call
 services:
   myproject:
     container_name: 'myproject'
-    image: 'username/myproject:20240904'
+    image: 'username/myproject:20250902'
     restart: unless-stopped
 ```