DEV Community: Atul Anand Oraon

Typescript extending types screws you at the most unexpected time

Atul Anand Oraon — Thu, 23 Oct 2025 21:54:52 +0000

So as we all get the issue with types. I too got it.

What happened to me?

So I was creating a simple express server. Things were fine until I got this big error message.


pnpm dev

> @ dev D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend
> cross-env NODE_ENV=DEV tsx watch src/index.ts

D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\express@5.1.0\node_modules\express\lib\application.js:161
    res.setHeader('X-Powered-By', 'Express');
        ^

TypeError: Cannot read properties of undefined (reading 'setHeader')
    at Function.handle (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\express@5.1.0\node_modules\express\lib\application.js:161:9)
    at app (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\express@5.1.0\node_modules\express\lib\express.js:38:9)
    at express (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\src\app.ts:34:21)       
    at Object.<anonymous> (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\src\app.ts:41:16)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Object.transformer (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\tsx@4.20.6\node_modules\tsx\dist\register-D46fvsV_.cjs:3:1104)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at Module.require (node:internal/modules/cjs/loader:1233:19)
    at require (node:internal/modules/helpers:179:18)

Node.js v20.15.1

I was confused I tried to rerun

tsconfig.json

{
  "compilerOptions": {
    "target": "es2016",
    "module": "commonjs",
    "lib": ["es6", "dom"],
    "outDir": "./dist",
    "rootDir": "./src",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "typeRoots": [
      "./node_modules/@types", // Include default @types
      "./src/types" // Path to your custom types directory
    ]
  },
  "include": ["src/**/*.ts", "src/types/**/*.d.ts"],
  "exclude": ["node_modules", "**/*.spec.ts"]
}

backend\src\types\express.d.ts

import { User } from "../generated/prisma";


declare global  {
    namespace Express{
        interface Request {
            user?: User| null;
        }
    }
}


pnpm dev

> @ dev D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend
> cross-env NODE_ENV=DEV nodemon src/index.ts

[nodemon] 3.1.9
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: ts,json
[nodemon] starting `ts-node src/index.ts`
D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:859
    return new TSError(diagnosticText, diagnosticCodes, diagnostics);
           ^
TSError: ⨯ Unable to compile TypeScript:
src/middlewares/auth.middleware.ts:33:9 - error TS2339: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'.

33     req.user = user;
           ~~~~
src/middlewares/auth.middleware.ts:47:14 - error TS2339: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'.

47     if (!req.user) {
                ~~~~
src/middlewares/auth.middleware.ts:51:36 - error TS2339: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'.

51     if ( requiredRole.includes(req.user.role) === false ) {
                                      ~~~~

    at createTSError (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:859:12)
    at reportTSError (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:863:19)
    at getOutput (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:1077:36)
    at Object.compile (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:1433:41)
    at Module.m._compile (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:1617:30)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Object.require.extensions.<computed> [as .ts] (D:\My Code\Projects\web-dev\full-stack\LEARNING\mycom\backend\node_modules\.pnpm\ts-node@10.9.2_@types+node@24.7.2_typescript@5.9.3\node_modules\ts-node\src\index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Function.Module._load (node:internal/modules/cjs/loader:1024:12)
    at Module.require (node:internal/modules/cjs/loader:1233:19) {
  diagnosticCodes: [ 2339, 2339, 2339 ]
}
[nodemon] app crashed - waiting for file changes before starting...

Finally after the hit and trials I got it working.

package.json

scripts:{
"dev": "cross-env NODE_ENV=DEV nodemon --watch 'src/**/*.ts' --exec 'ts-node --files' src/index.ts",
"build": "tsc",
"start": "cross-env NODE_ENV=PROD node dist/index.js"
}

tsconfig.json

{
  "compilerOptions": {
    "target": "es2016",
    "module": "commonjs",
    "lib": ["es6", "dom"],
    "outDir": "./dist",
    "rootDir": "./src",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "typeRoots": [
      "./node_modules/@types", // Include default @types
      "./src/types" // Path to your custom types directory
    ]
  },  
  "include": ["src/**/*.ts", "src/types/**/*.d.ts"],
  "exclude": ["node_modules", "**/*.spec.ts"]
}

backend\src\types\express\index.d.ts

import { User } from "../../../generated/prisma";

declare module "express" {
  export interface Request { 
    user?: User | null;
  }
}

Now let me explain the dev script

Development Script:

Always use a dev script like:

"dev": "nodemon --watch 'src/**/*.ts' --exec 'ts-node --files' src/index.ts"

The --files flag is crucial to load type augmentation files automatically.
When you see TS errors like “Property ‘user’ does not exist on type ‘Request’”:
- Double-check module augmentation syntax.
- Make sure your dev script includes --files for ts-node.
- Restart your TypeScript server/IDE after changing types or config.

uri mismatch issue oauth2 | google | Error 400: redirect_uri_mismatch

Atul Anand Oraon — Sun, 06 Apr 2025 20:23:11 +0000

How I Solved My Google OAuth2 Redirect URI Error That Was Hiding in Plain Sight 😒

So I happened to use OAuth2 by Google, but I was getting this error despite having the exact correct path—I copied it straight from my browser’s search bar.

But to my surprise, I was still getting the error. I was utterly confused. 😵‍💫

So this is what I tried:

Checked the Network tab to see if anything was wrong. It looked good.
Copied the exact address from the search bar into the origin and callback fields.
What actually worked: I clicked on error detail 🤯

Then came the twist...

I knew I had to check the error details here too. So I clicked it, and to my surprise:

Now, this was shocking. I saw the lock icon up there while copying, so I assumed it was https.

But in reality—it was actually http.

This is evil in plain sight, and honestly, this kind of thing shouldn't even happen. 😒

The fix that worked:

I added http (instead of https) to both the origin and the redirect URI.

Boom. Issue resolved.

So yeah—next time, take a close look at the error message and match everything properly.

Because if this happened in plain sight, anything can.

I had already tried all other possibilities and finally ended up solving it with this simple change.

😋 I didn’t include screenshots of the Network tab to avoid overwhelming you, but trust me—I went deep.

Headers, cookies, requests, responses, shared files—you name it.

But yeah, sometimes it's best to try the simple stuff first.

Moral of the story:

Don’t trust the lock icon. Trust your logs and error details. 👀

Auto-Delete Files in S3: A Beginner's Guide

Atul Anand Oraon — Sat, 08 Feb 2025 14:55:31 +0000

Auto-Deleting S3 Files: A Lazy Dev's Best Friend 🦥

Hey folks,

I'm back after a long break! Let's dive straight into something useful. As the title says, you're gonna learn how to automatically delete files from your S3 bucket.

Now, you might be thinking, "Why not just delete them programmatically?" That's a valid thought! You could write a script and use the AWS SDK (boto3, anyone?). But, hear me out: it's often better to leverage S3's built-in lifecycle rules for auto-deletion. It saves you API calls, reduces the complexity of your code, and lets AWS handle the heavy lifting. Why reinvent the wheel, right?

So, let's get started. This is so simple, it's almost cheating. 😉

Steps to Auto-Delete Your S3 Files

Search for S3 in the AWS Console

Yeah, the good ol' search bar. Type "S3" and hit enter. You know the drill.

Select the bucket you want to use.

Choose the S3 bucket where you want to enable automatic file deletion.

Go to the Management tab

This is where the magic happens.

Go to management

Create a Lifecycle Rule

Click that beautiful "Create lifecycle rule" button.

Set the scope

Choose whether you want the rule to apply to all objects in the bucket or only to specific objects based on a prefix (folder) or tags. For most simple cases, "This rule applies to all objects in the bucket" is what you want. Don't forget to check the acknowledgement box.

Add the expiration time

This is the key part! Select "Expire current versions of objects" and set the number of days (or even hours!) after which you want the files to be automatically deleted. For example, setting it to 3 will delete files older than 3 days.

Lifecycle Applied! 🥳

Click "Create rule", and you're done! S3 will now automatically delete files based on your rule. Keep in mind that it might take a little while for the rule to kick in .

When is this useful?

Log file management: Automatically delete old log files to save on storage costs.
Temporary files: If you're storing temporary files in S3, set a lifecycle rule to clean them up after a certain period.
Backups: Rotate backups by automatically deleting older versions.

Alternatives

While lifecycle rules are generally the easiest way to go, you can also use the AWS CLI or SDKs to delete files programmatically. For example, you could use the AWS CLI command aws s3 rm s3://your-bucket-name/path/to/files --recursive in a cron job. However, this requires you to manage the scheduling and execution of the script.

Useful and cool Linux tricks

Atul Anand Oraon — Fri, 13 Sep 2024 16:47:44 +0000

Hi folks

I recently joined th community fcall on the discord server of the Growin Community. There we had a Linux session in which we learn't quite some handy tricks with the Linux.

If you do not own a linux machine do not worry. You can use

1 Killer koda
Just choose the ubuntu from here
2 copy.sh

Alright you are all set to get your hands on the terminal.

3,2, 1 Go 🔫🚀

LINUX Tricks

To execute a previous command:
- history — prints the history of commands.
- !<cmd_no> — executes a command from history based on its number.
To copy and paste lines in vim:
- Esc + 10yy — copies 10 lines.
- Paste with p to insert after the cursor.
To perform a reverse search:
- Ctrl+R — reverse search through the command history.
To count lines in a file:
- wc -l aks.txt — counts and lists the number of lines.
Yanking (copying) in vim:
- yy — yanks (copies) the current line.
- Esc + 5yy — yanks (copies) 5 lines.
- Paste with p after yanking.
Navigating in vim:
- Esc + :1 — jumps to line 1.
- :set nu — enables line numbers.
- Esc + Shift+G — moves to the end of the document.
Deleting in vim:
- Esc + dG — deletes everything from the current line to the end of the document.
- Esc + u — undoes the last change.
Finding unique adjacent lines in a file:
- uniq -c — looks for unique adjacent lines.
Sorting, unique filtering, and counting occurrences:
- cat aks.txt | sort | uniq -c — lists all unique lines in aks.txt with their counts after sorting.

That's it you got a lot from this article do like it and share any comments
you want to. DO not shy away.

See you next time

Useful and cool Linux and Vim tricks

Atul Anand Oraon — Tue, 10 Sep 2024 17:15:23 +0000

Hi folks,

I recently joined the community call on the Discord server of the Growin Community. We had a Linux session where we learned some handy tricks with Linux.

If you don’t own a Linux machine, don’t worry! You can use:

Killer Koda — Just choose Ubuntu from here.
copy.sh

Alright, you're all set to get your hands on the terminal.

3, 2, 1, Go! 🔫🚀

LINUX Tricks

To execute a previous command:
- history — prints the history of commands.
- !<cmd_no> — executes a command from history based on its number.
To copy and paste lines in vim:
- Esc + 10yy — copies 10 lines.
- Paste with p to insert after the cursor.
To perform a reverse search:
- Ctrl+R — reverse search through the command history.
To count lines in a file:
- wc -l aks.txt — counts and lists the number of lines.
Yanking (copying) in vim:
- yy — yanks (copies) the current line.
- Esc + 5yy — yanks (copies) 5 lines.
- Paste with p after yanking.
Navigating in vim:
- Esc + :1 — jumps to line 1.
- :set nu — enables line numbers.
- Esc + Shift+G — moves to the end of the document.
Deleting in vim:
- Esc + dG — deletes everything from the current line to the end of the document.
- Esc + u — undoes the last change.
Finding unique adjacent lines in a file:
- uniq -c — looks for unique adjacent lines.
Sorting, unique filtering, and counting occurrences:
- cat aks.txt | sort | uniq -c — lists all unique lines in aks.txt with their counts after sorting.

That's it! You’ve learned a lot from this article. Do like it and share any comments you have. Don’t shy away!

See you next time!

React Rendering the component Twice

Atul Anand Oraon — Wed, 22 May 2024 21:45:13 +0000

Hi Techies

If you are using React, you would definitely be using the useEffect hook right?

What if I told you that the React Renders twice and it's a simple bug 🤨️?
Yeah that's right it's a very small bug, but yet underlooked, although it's only on our local system and not on the actual production build.
But wait a minute, even if it is just in the dev mode. we use vite or other

tools to keep the app running and reflect the changes live. Also, most of us have turned on the auto-save option as the cherry on top.

This becomes a hectic challenge when we use useEffect to make the
API calls. As some free APIs have a limit of 100 calls a day, so I would recommend turning off the auto-save on your IDE to stay safe.

Now After this small story, what would be a feasible solution you may ask?
I have a very simple yet effective solution for Ya. So great if you are following along. Let's see how to tackle this bully.

First of we would like to have some environment variables. Yeah, this would be beneficial, you could choose to name it environment or mode. Here let's go with the environment

In your .env.local you can have it like

VITE_Environent="DEV"
# if using vite
REACT_APP_Environent="DEV"
# If using create-react-app

Have a file to store your environment variables like this

env.config.ts

const RAPIDAPI_KEY: string = import.meta.env.VITE_RAPIDAPI_KEY;
const RAPIDAPI_HOST: string = import.meta.env.VITE_RapidAPI_Host;
const ENVIRONMENT: string = import.meta.env.VITE_Environent;
const ENVS = {
 RAPIDAPI_KEY: RAPIDAPI_KEY,
 RAPIDAPI_HOST: RAPIDAPI_HOST,
 ENVIRONMENT: ENVIRONMENT, 
};

export default ENVS;

I am exporting it like so, to avoid the typos as only by console logs you can detect them so better to do it here once and import and use them elsewhere. Also, look at the naming convention and replace the VITE_ with REACT_APP_ for a smooth experience.

Now, here comes the juicy part for which you have been reading this blog
the proper way to do it.

main.tsx

import React, { memo } from "react";
import ReactDOM from "react-dom/client";
import { Route, BrowserRouter as Router, Routes } from "react-router-dom";
import App from "./App.tsx";
import "./index.css";
import { Provider } from "react-redux";
import { store } from "./state/store.ts";
import ProductsPage from "./pages/ProductsPage.tsx";
import NotFound from "./pages/NotFound.tsx";
import ENVS from "./env.config.ts";
const renderApp =() => (
 <Provider store={store}>
 <Router>
 <Routes>
 <Route path="/" element={<App />}>
 <Route path="products" element={<ProductsPage />} />
 </Route>
 <Route path="*" element={<NotFound />} />
 </Routes>
 </Router>
 </Provider>
)

console.log("ENVS.ENVIRONMENT", ENVS.ENVIRONMENT)
// Conditionally wrap in React.StrictMode based on the environment
// As it is the one causing this issue
// React.StrictMode 
const app =
 ENVS.ENVIRONMENT !== "DEV" ? (
 <React.StrictMode>{renderApp()}</React.StrictMode>
 ) : (
 renderApp()
 );

ReactDOM.createRoot(document.getElementById("root")!).render(app);

Here we have just a simple little change.
We made an arrow function renderApp which is a simple JSX.element
and conditionally put it inside the <React.StrictMode> if the the Environment is not DEV . It does the job and we get the best of both worlds.

Also if you feel at any moment you need the React.StrictMode , you can
easily do so by just putting the renderApp() in the React.StrictMode .

I know this is going to surely help. Keep coding.

How to cleanup Linux | Ubuntu

Atul Anand Oraon — Sun, 05 May 2024 11:00:19 +0000

Well, I recently got alerts on my local system getting full. But wait a minute.
I do not have a lot on my system. I got sus about it.
Just the usual thing which will come to my mind is to check, if, my Downloads dir got too big. Sheesh, not it isn't weighing just 16.5GB light.
Well, that's nothing.

I then went on to look at the rest of my folder structure. Nothing was to be found. Well, then I thought let's get on the journey to the West ;)

Sometimes we get to a point where despite very less or no usage

our Linux seems to get full. As if it got fed some nice extra large pizza with some extra cheese and chili flakes.

It is kind of funny, I had to look a lot for it.

With a lot of trial and error, I accumulated these ways.

Well, this tutorial also taught me a lot.

Youtube Tutorial

First off let's get a bit commanding.
Ahem, just paste this into your terminal to see the disk usage

For the HDD use this
df -TH | grep "/dev/sda"

For the nvme/ssd use this
df -TH | grep "/dev/nvme*"

The output would be like this


/dev/nvme0n1p6 ext4      194G  120G   65G  66% /
/dev/nvme0n1p5 ext4      990M  507M  415M  56% /boot
/dev/nvme0n1p1 vfat      269M   73M  197M  27% /boot/efi

Let's now remove any unwanted dependencies

sudo apt-get autoremove && sudo apt-get autoclean

The auto clean will remove any broken library files.

Further remove the unwanted configs of removed dependencies

This command will purge any packages that were previously removed but left configuration files behind.

sudo apt purge $(dpkg -l | awk '/^rc/ {print $2}')

Here's how it works:

    dpkg -l lists all installed packages
    awk '/^rc/ {print $2}' filters the output to only include 
packages with an 'rc' status (removed with config files left behind) 
and prints the second field (package name)

Let's clear some cache

So in the Linux, our cache can be in two places

/var/cache
~/.cache
To clean them simply do this.

~ via  v20.10.0 
┌───────────────────
│
└─> du -sh .cache/
153M    .cache/

~ via  v20.10.0 
┌───────────────────
│
└─> cd .cache/

~/.cache 
┌───────────────────
│
└─> sudo apt clean

This way you can clean your cache dir same goes for the /var/cache

System level files

As we know, systemd oversees both kernel and user-level processes, serving as the init process launched by the kernel during boot. Following this, systemctl orchestrates the startup of systemd and other crucial processes, first at the system level and then at the user level.
journald is one such process which handles the logging.

We can use journalctl to handle the logs.

Let's just simply type sudo journalctl

Smack it, You will se something like this in the output.

May 05 02:42:20 idea systemd-journald[447]: System Journal (/var/log/journal/13>
May 05 02:42:20 idea sudo[98578]: pam_unix(sudo:session): session closed for us>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>

BTW, to exit this log press q, or, you may prefer to watch all of it by pressing down arrow or scrolling.

Now let's make things simpler and see the previous boot logs.
Below is the command for that.
sudo journalctl -b

It will show you the similar log again.

Now lets list all the journals

journalctl --list-boots

And you would have something like this

-2 af75e0d9a21a45f28653826f41945f0e Sun 2024-05-05 02:42:20 IST—Sun 2024-05-05 >
-1 a68bb606747340c298469ca6d9c0a1d6 Sun 2024-05-05 13:29:28 IST—Sun 2024-05-05 >
 0 27d70b75e7624865bb37107c7d054b0c Sun 2024-05-05 14:48:15 IST—Sun 2024-05-05 >
lines 1-3/3 (END)

You might find 8 to 10 entries too.

Now you can watch for the specific date, logs by simply wirting its index as displayed.

say sudo journalctl -b -2

You will have a nice list of logs.

May 05 02:42:20 idea systemd-journald[447]: System Journal (/var/log/journal/13>
May 05 02:42:20 idea sudo[98578]: pam_unix(sudo:session): session closed for us>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>
May 05 02:42:21 idea python[98637]: /usr/local/bin/cpufreqctl.auto-cpufreq: lin>

You can also watch since a particular duration say 4 hours.

Just type ahead sudo journalctl --since "4 hours ago"

Yet again you will have a lovely logs

May 05 13:29:28 idea kernel: Linux version 6.5.0-060500-generic (kernel@kathleen) (x86_64-linux-gnu-gcc-13 (Ubuntu >
May 05 13:29:28 idea kernel: Command line: BOOT_IMAGE=/vmlinuz-6.5.0-060500-generic root=UUID=08169e91-a06a-4efc-b9>
May 05 13:29:28 idea kernel: KERNEL supported cpus:
May 05 13:29:28 idea kernel:   Intel GenuineIntel
May 05 13:29:28 idea kernel:   AMD AuthenticAMD
May 05 13:29:28 idea kernel:   Hygon HygonGenuine
May 05 13:29:28 idea kernel:   Centaur CentaurHauls
May 05 13:29:28 idea kernel:   zhaoxin   Shanghai  
May 05 13:29:28 idea kernel: BIOS-provided physical RAM map:
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009afffff] usable
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000009e00000-0x0000000009efffff] usable
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f11fff] ACPI NVS
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x0000000009f12000-0x000000009fffefff] usable
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x000000009ffff000-0x000000009fffffff] reserved
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x00000000a0000000-0x00000000a2363fff] usable
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x00000000a2364000-0x00000000a4563fff] reserved
May 05 13:29:28 idea kernel: BIOS-e820: [mem 0x00000000a4564000-0x00000000a456cfff] usable
Ma

Now you might want to know how much disk usage does it takes.
Here's the command to know that.

sudo journalctl --disk-usage

Output will be like

Archived and active journals take up 48.0M in the file system.

Now to mark the active journal logs as archived we need to rotate it, kind of like, closing the notebook.
Here's the command

sudo journalctl --rotate

Well this might be a bit confusing. Let me simplify it for you.
You can think of it as the journalctl is journaling. You went ahead
and told it to stop using this page and start writing the rest of the stuff
on the new page. That's what it is at core.

Taking the backup

Now for some reason you decide to take the backup of the logs.
As we know, the logs are really precious.

You can do it simply like this

sudo cp -r /var/log/journal/* /path/to/backup/directory/

Or if you want to zip it

sudo tar czvf journal_backup.tar.gz /var/log/journal/*

Now what if, you want to backup last 5 logs.
I got you

here is the command for it

sudo cp -r $(ls -lt /var/log/journal/ | grep systemd-journal | awk '{print $NF}' | head -n 5) /path/to/backup/directory/

Here is the tar way

sudo tar czvf journal_backup.tar.gz $(ls -lt /var/log/journal/ | grep systemd-journal | awk '{print $NF}' | head -n 5)

The awk '{print $NF}' part extracts the file or directory names from the output.

Deleting the journals

Now we have to delete a few journals. Consdier it like vacuum cleaning stuff.
Let's delete everything older than yesterday(the previous day)

sudo journalctl --vacuum-time 1d

This is my output since I already cleaned yesterday.

Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/13da9b9ba4b64ddebab4fcc2387bfa6d.
Vacuuming done, freed 0B of archived journals from /var/log/journal.

Next you can again check your journalctl disk usage.

sudo journalctl --disk-usage

Archived and active journals take up 64.0M in the file system.

Cleaning the thumbnails in the cache

You might do it if you like it.
Here's the command for that.

sudo rm -rf ~/.cache/thumbnails/*

Removing the old revisions of snaps

For my snappy friends I got you too.
You should put the below in a shell file and then run or
if you decide to directly paste it don't copy the set -eu part


# Set DISPLAY and XAUTHORITY environment variables to run in the 
# graphical environment without this notify-send does not work on my 
# machine

DISPLAY=:0
XAUTHORITY=~/.Xauthority

set -eu

LANG=C snap list --all | awk '/disabled/{print $1, $3}' |
    while read snaprename revision; do 
        snap remove "$snapname" --revision="$revision"
    done
DISPLAY=:0 notify-send "Cleaned the snappy snaps revisions ;)"

Let's have some details about what it does.

set -eu: This line sets two options for the shell:
-e (errexit): Causes the shell to exit immediately, if any command exits with a non-zero status (i.e., an error).
-u (nounset): Treats unset variables as an error when they are referenced.
LANG=C : sets the language to English
awk '/disabled/{print $1, $3}' : looks for lines containing the word "disabled" and prints the 1st and 3rd field
while read snapname revision; do: This starts a while loop, that reads each line of output from the awk command. It assigns the 1st field to the variable snapname and the 3rd field to the variable revision.
snap remove "$snapname" --revision="$revision": This command removes the specified snap package ($snapname) at the specified revision ($revision) using the snap remove command.

Docker Basics beginner to pro

Atul Anand Oraon — Wed, 10 Apr 2024 19:41:19 +0000

Docker

Use Docker without sudo

For this, we need to add the user to the docker mod.

Below is the terminal command:

sudo usermod -a -G docker userName
#or
sudo usermod -a -G docker $USER

Now we need to logout and login again to see effects.

Pull and run a public docker image from the docker hub.

Here’s the command

version is optional

docker run image:version

Docker advantages

1 Its light

2 Its fast

3 It allows to have different configuration layer

i.e. We can separate it form the actual OS configs.

4 We also get the benefit of running the same image

with different versions simultaneously on the same computer.

Basic Commands

docker pull imageName:version

This gets the public image from docker hub.

The version is optional

docker images

It shows the list of all images

REPOSITORY               TAG       IMAGE ID       CREATED         SIZE
redis                    latest    e10bd12f0b2d   7 days ago      138MB

docker run imageName:version

Here things get interesting.

If you mentioned the version while pulling, you must do so now too.

Else docker will pull the latest version of it and then run it.

💡 Well, you can stop it by just doing a Ctrl+C that's it.

docker ps

lists down all the currently running images.

💡 We can also use Ctrl+C to stop the image

docker run -d imageName

To run the image in detached mode i.e. now Ctrl+C won’t work on it.

It runs in detached mode

example

docker run -d -p3000:3000 --name node-app example-node

Now to stop a detached image

We need to

💡 docker ps
Now we have the id
We can stop it simply using
docker stop id

docker ps -a

This prints the whole history.

From here we can start a container with its id.

by using the command

docker start id

docker run -p:containerPort image:version

Now the command above looks a bit big.

Let me break it down.

Let’s first have an example

docker run -p9000:6379 -d redis

Result

docker ps
CONTAINER ID   IMAGE     COMMAND                  CREATED          STATUS          PORTS                                       NAMES
5aeaf8ee3849   redis     "docker-entrypoint.s…"   14 seconds ago   Up 11 seconds   0.0.0.0:9000->6379/tcp, :::9000->6379/tcp   xenodochial_curran

This helps us bind a host port to the container port.

This is really helpful when we want to run 2 versions of the same image.

We can bind them to 2 different ports.

docker logs id

This helps us see the logs of a container.

This helps us solve bugs and errors.

💡 we can also use names instead of id here

Naming the docker containers

docker run —name custom-name image:version

docker run -p9000:6379 -d --name redis_latest redis
docker run -d -p9001:6379 --name redis_old redis:6.2

docker rm container_id_or_name

This command removes the container

docker rm redis_old redis_latest

Remove all containers

💡

docker ps -q | xargs docker stop
docker ps -q | xargs docker rm

To get the interactive terminal of a container

docker exec -it container_id_or_name /bin/bash

To exit the terminal simply Enter exit

Here -it stands for interactive mode.

Docker Volumes

Creating a Volume

You can create a volume explicitly using the docker volume create command:

docker volume create my-volume

This creates a new volume named my-volume that Docker will manage.

Running a Container with a Volume

When running a container, you can mount the volume using the -v or --mount flag:

docker run -d --name my-app -v my-volume:/app myapp:v1

This mounts the my-volume volume to the /app directory inside the container. Any data written to /app will be stored in the my-volume volume on the host.

Inspecting Volume Contents

You can inspect the contents of the volume on the host machine. The exact location depends on your Docker storage driver, but typically it will be under /var/lib/docker/volumes/. For example:

ls /var/lib/docker/volumes/my-volume/_data

This will list the files stored in the volume.

## Persisting Data

If the container crashes or is removed, the data written to the volume will persist on the host. You can then attach the volume to a new container to access the data:

docker run -d --name new-app -v my-volume:/app myapp:v2

The new container will have access to the same data as the previous container.

Sharing Volumes Between Containers

Volumes can be mounted to multiple containers simultaneously. This allows containers to share data:

docker run -d --name app1 -v my-volume:/data app1:v1
docker run -d --name app2 -v my-volume:/data app2:v1

Both app1 and app2 will have read-write access to the /data directory which points to the my-volume volume.

Docker volumes provide a way to persist data outside the container lifecycle. This ensures important data is not lost when containers are removed or crash. Volumes can be shared between multiple containers and their contents can be inspected directly on the host.

Thanks for making it to the very last. Since you read this do consider
leaving some comments.

Also you might find this post useful

https://dev.to/oatula/making-backup-of-a-docker-volume-1la9

Making backup of a docker volume

Atul Anand Oraon — Sun, 31 Mar 2024 19:10:30 +0000

Making a backup of the database

You can use it for any type of container not just for the database.

💡️ Don't be afraid of the --rm flag

It is not removing your container it just removes

🐧️alpine Linux container for using the cp command.

Which is a Linux command

The command will be like this.


docker run --rm -v volume_id:/volume -v /path/to/backup/directory:/backup alpine cp -a /volume/. /backup/

SIMPLE Explanation

docker run : run a command in a new container.
--rm : remove the container after it exits.
-v volume_id:/volume : mount the volume with id volume_id to /volume in the container.
-v /path/to/backup/directory:/backup : mount the host[our computer or server] directory /path/to/backup/directory to /backup in the container.
alpine : the image to use, its a lightweight Linux image.
cp -a /volume/. /backup/ : copy the contents of the volume to the backup directory on the host machine where it is being run.

So if you run locally it will be on your computer else

it will be on the server if you run it on the server.

[BOOKISH EXPLANATION] Specific questions regarding the command

:/volume and :/backup:
- In the command docker run --rm -v 7ade41ba2f490a4ccbe15b442baa7071a8bf57c4a0cb5cf250bbad845994ef4f:/volume -v /path/to/backup/directory:/backup alpine cp -a /volume/. /backup/, the :/volume and :/backup parts indicate the mount points within the container. When you use the -v option with Docker, you specify the volume binding in the format host_path:container_path. So 7ade41ba2f490a4ccbe15b442baa7071a8bf57c4a0cb5cf250bbad845994ef4f:/volume means you're mounting the Docker volume 7ade41ba2f490a4ccbe15b442baa7071a8bf57c4a0cb5cf250bbad845994ef4f to /volume inside the container, and /path/to/backup/directory:/backup means you're mounting the host directory /path/to/backup/directory to /backup inside the container.
alpine:
- alpine is the name of the Docker image being used to run the temporary container. In this case, it's an Alpine Linux image, which is commonly used due to its small size and efficiency for tasks like this.
cp -a /volume/. /backup/:
- This is the cp command that copies files.
- -a is an option that preserves the original attributes of the files being copied, such as permissions and timestamps.
- /volume/ is the source directory from which files are being copied.
- . at the end indicates that the entire contents of the source directory (including hidden files) are being copied.
- /backup/ is the destination directory where the files are being copied to.

This command effectively mounts the Docker volume and a backup directory into an Alpine

Linux container, then copies the contents of the Docker volume to the backup directory

within the container. This allows you to create a backup of the data stored in the Docker volume.

Setting the cookies using the JS, axios and expressJS

Atul Anand Oraon — Sat, 02 Mar 2024 13:34:46 +0000

Hi all
recently I am learning about the auth.
I tried setting the accessToken and refreshToken for the auth.

Initially decided to use fetch for it. It did not work in my case. Exhausted all the combination of credentials.

credentials:true,
credentials:include,
etc.

I was really pissed and sad for like 3-4 days.

Finally decided to switch to axios also made some adjustment to my backend and it started working.

Let me show you my code.

My axios request

 const loginCall = () => {
// You may get these data from the relevant selector
let data= {
        email: "dummy@mail.com", 
        password: "123",
      }
    const options = {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
      },
      withCredentials: true, // Ensure Axios includes cookies in the request
    };

    axios("http://localhost:8002/auth/login", data,options)
      .then((response) => {
        // Check if response status is in the 200 range
        if (response.status >= 200 && response.status < 300) {
          console.log("response is: ", response);

          // Print all headers from response
          console.log("headers are: ");
          console.log(response.headers);

          let responseData = response.data;
          console.log(responseData);

          let accessToken = responseData.accessToken;
          console.log("access token is: ", accessToken);

          // Set the accessToken cookie correctly
          document.cookie = `accessToken=${accessToken}; path=/; SameSite=Strict; expires=${new Date(
            Date.now() + 1000 * 60 * 5
          ).toUTCString()}`;
          console.log("cookie is: ", document.cookie);

          // The refreshToken HttpOnly cookie will be automatically stored by the browser
        } else {
          throw new Error("Network response was not ok");
        }
      })
      .catch((err) => console.error(err));
  };

Put this in your index.js/server.js

const express = require("express");
const app = express();
let cors = require("cors");
app.use(
  cors({
    origin: "localhost",
    credentials: true,
  })
);

To add multiple domains do this.
origin: ["http://localhost:3000", "http://example.com", "https://subdomain.example.com"]

now the below code in your

let express = require("express");
let bcrypt = require("bcrypt");
let jwt = require("jsonwebtoken");
let User = require("../models/user-model");

// Login Route with JWT
router.post("/login", async (req, res) => {
  try {
    const { email, password } = req.body;

    // Check if user exists
    const user = await User.findOne({ email });

    if (!user) {
      return res
        .status(401)
        .json({ message: "Authentication failed, email not found" });
    }

    // Check password
    // @ts-ignore
    const isMatch = await bcrypt.compare(password, user.password);

    if (!isMatch) {
      return res
        .status(401)
        .json({ message: "Authentication failed, wrong password" });
    }

    // Generate JWT token with expiration time of 1 month (in seconds)
    // jwt.sign({ id user._id, exp Math.floor(Date.now() / 1000) + (60 * 60 * 24 * 30) }, SECRET);
    //@ts-ignore
    const { accessToken, refreshToken } = signToken(user);

    // httpOnly token way for the deployment
    // res.cookie("accessToken", accessToken, {
    //   httpOnly: false,
    //   sameSite: "none",
    // });
    const expires = new Date(Date.now() + 60 * 60 * 1000);
    res.cookie("refreshToken", refreshToken, {
      httpOnly: true,
      expires: expires,
      sameSite: "none",
    });

    res
      .status(201)
      .json({ message: "User created successfully", accessToken: accessToken });
  } catch (error) {
    console.log(error);
    res.status(500).json({ message: "Server Error" });
  }
});

Pardon me for a lot of commented code.

I have removed some yet some remains.

So for me this code worked in the firefox browser

    const expires = new Date(Date.now() + 60 * 60 * 1000);
    res.cookie("refreshToken", refreshToken, {
      httpOnly: true,
      expires: expires,
      sameSite: "none",
    });
   res.send("refresh Token sent")

For my friend using Brave browser the below code worked.

const expires = new Date(Date.now() + 60 * 60 * 1000);
    return res
      .status(200)
      .cookie("refreshToken", refreshToken, {
        path: '/',
        httpOnly: true,
        secure: true,
        expires: expires,
        sameSite: "none",
        domain: "localhost",
      })
      .json({
        accessToken: accessToken,
        id: user._id,
        role: user.role,
        firstname: user.firstname,
        lastname: user.lastname,
        email: user.email,
        message: "User logged In Successfully",
    });

Now let me explain you these settings
First of all you must add the origin and credentials. Its a must. Else your tokens won't be sent or set.

const expires = new Date(Date.now() + 60 * 60 * 1000);
    res.cookie("refreshToken", refreshToken, {
        path: '/',
        httpOnly: true,
        secure: true,
        expires: expires,
        sameSite: "none",
        domain: "localhost",
      }

Now these cookie settings.

path: / This means the cookie is valid across all the path.
If you want this to be valid to certain parts only say

/protected

httpOnly:true This option is very crucial here. It tells the browser don't allow any JS touch it. Which means its totally secure. This is protected from the Cross Origin Attack

secure:true This option means that browser will only send this cookie over https connection not http.
My reccomendation is to make a variable named cookieOptions or refreshTokenOptions.

Try setting the secure:true in the production environment.
As you will go nuts when your backend on local system does not
get the cookies. As almost all of us have our local working on http.

let cookieOptions = {
    httpOnly: true,
    sameSite: "none",
  }

if(process.env.NODE_ENVIRONMENT=="production")
  cookieOptions.secure= true;

const expires = new Date(Date.now() + 60 * 60 * 1000);
expires: expires,

This sets the expiry time for the cookie to 1 hour.

You can set the time as per your choice.

My personal reccomendations are 3hour to a day.

Not more than that.

Also the time has to be given in miliseconds.
So to set 1 hour = 60mins X 60sec X 1000 milisec

sameSite: "none" is used to send the cookies cross-site requests,

which basically means your backend and client can be on different ports and even different addresses.

domain: "localhost" means its valid for only for localhost domain.
You may want to have multiple domains do it like this.

    domain: ["localhost", "example.com", ".subdomain.example.com"]```