Tutorials covering the tools that developers use every day — version control, editors, build systems, package managers, containers, and the command-line utilities that make work faster. Each chapter is standalone, built around real examples and verified commands.
A single-page reference for the Git commands you’ll reach for most. Grouped by task, with a short description of what each does. Bookmark it — you’ll come back often. Key point: This isn’t a tutorial — it’s a lookup table. When you know what you want but not the exact syntax, find the command here….
The two files serve opposite purposes in the same dependency system. package.json is the manifest: it declares the project’s metadata, scripts, and the ranges of acceptable dependency versions. package-lock.json is the resolution: it records the exact version of every package that was actually installed, including transitive dependencies that package.json never mentions. The distinction matters because…
Once a container is running, the next question is how to observe and interact with it. A container is isolated by design, so you cannot simply open a terminal into it or read its output from the host. Docker provides three commands for this: docker logs retrieves the output a container has already produced, docker…
8. Git Test Q&As a. Git Fundamentals b. Introduction to Remote Repositories c. Connecting Local to Remote d. Git Branching Questions e. Basic Branch Commands 12 .Why would you use git merge –no-ff instead of allowing fast-forward merges?You would use git merge –no-ff to force Git to create a three-way merge commit, even if a…
npm installs packages in two locations, and the flag determines which one. A local install, the default, places the package in the node_modules folder of the current project and records it in package.json. A global install, triggered by -g or –global, places the package in a system-wide location (/usr/local/lib/node_modules on most Unix systems) and makes…
Running a container is only half the job. Knowing what it is actually doing—what configuration it was created with, how much CPU and memory it is consuming, what processes it is running—requires a set of inspection commands that read metadata rather than run new operations. docker inspect returns the full JSON description of a container,…
Git 1a Git Fundamentals Understanding Version ControlGit 1b Installing GitGit 1c Initial Git ConfigurationGit 1d The Git Workflow Local Repository Git 2a Introduction to Remote RepositoriesGit 2b Connecting Local to RemoteGit 3a Understanding BranchesGit 3b Basic Branch CommandsGit 3c Resolving Merge ConflictsGit 4a RebasingGit 4b Stashing ChangesGit 4c Cherry PickingGit 4d Tagging ReleasesGit 4e Ignoring…
npx is the command that resolves the tension between local and global installation. It runs a package’s binary without requiring a permanent install, checking first in the local node_modules/.bin, then in the npm cache, and downloading temporarily only if the binary is not found anywhere . The command ships with npm since version 5.2.0, so…
A container’s filesystem is not a single block of disk space. It is a stack of read-only image layers with a thin writable layer placed on top when the container starts. Every file the image contains lives in the read-only layers, and every change the running container makes—writing a log, modifying a config, creating a…
An npm script is a named shell command stored in package.json and executed by npm with a modified environment. The modification is the point: npm prepends node_modules/.bin to the PATH before running the script, so any binary provided by a locally installed dependency can be invoked by name without the full path . This is…