Skip to content

Instantly share code, notes, and snippets.

View manzil-infinity180's full-sized avatar
🦉
Focusing

Rahul Vishwakarma manzil-infinity180

🦉
Focusing
View GitHub Profile
@manzil-infinity180
manzil-infinity180 / docker-clean-up.md
Last active August 18, 2025 19:01
Clean your Mac System Data - My Docker takes near 1TB space
$ docker system df                
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          0         0         0B        0B
Containers      0         0         0B        0B
Local Volumes   13        0         31.52GB   31.52GB (100%)
Build Cache     0         0         0B        0B
List All Volumes:
@zcaceres
zcaceres / Nested-Routers-Express.md
Last active August 14, 2025 13:53
Child Routers in Express

Nested Routers in Express.js

Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params when you had a long URI with multiple parameters and nested routes.

Let's say you're building routes for a website www.music.com. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.

At our application level, we could first have a Router to handle any requests to our albums.

const express = require('express');