liveBook · Manning

Repository

A software repository is an organized storage location or collection of project files and related artifacts, often managed with version history and change tracking.

How 10 Manning books explain it

Platform Engineering on Kubernetes

A Git repository is a version-controlled storage location containing project files and their revision history.

How it is used
Connects source changes with service pipelines and uses environment configuration repositories to drive deployment workflows.
How deep it goes
Explains repository contents, webhook triggers, organizational choices, and GitOps synchronization, but stops short of Git internals.
Examples
Uses src directories, Dockerfiles, Kubernetes manifests, environment configurations, webhooks, and Argo CD synchronization as concrete artifacts.
What you can do after
Configure service and environment pipelines around repository changes, deployment inputs, version declarations, and GitOps synchronization.

Read how Platform Engineering on Kubernetes explains repository →

Road to Kubernetes

A Git repository is a directory managed by Git that stores files, metadata, and version history.

How it is used
Provides tracked application code for sharing, production pulls, and deployment automation.
How deep it goes
Works through initialization, status, commits, remotes, and push troubleshooting; leaves Git branching beyond scope.
Examples
Uses separate Python and Node.js repositories, a GitHub remote, and a virtual-machine remote.
What you can do after
Operate/configure it by initializing local repositories, recording changes, connecting remotes, and pushing application code.

Read how Road to Kubernetes explains repository →

Automating API Delivery

A Git-managed repository containing files, revision history, and metadata for collaborative versioned development.

How it is used
Uses repositories as versioned homes for API definitions and declarative gateway configurations that teams can change through Git workflows.
How deep it goes
Explains repository roles, PR review, and pipeline integration, but does not specify Git commands or repository setup steps.
Examples
Uses a dedicated API-definition repository and an environment repository holding API gateway deployment settings.
What you can do after
Operate/configure it by keeping API definitions and gateway settings in Git, reviewing changes through PRs, and connecting checks to CI/CD.

Read how Automating API Delivery explains repository →

Build Python Web Apps with Streamlit

A Git repository is a project directory managed by Git that stores files together with their version history and staging metadata.

How it is used
Supports storing, versioning, and publishing application code for deployment through Streamlit Community Cloud.
How deep it goes
Explains repository creation, initialization, staging, committing, remote configuration, and pushing, but not broader Git workflows.
Examples
Uses a Streamlit to-do list containing todo_list.py and task.py, with command-line commands for committing and pushing it.
What you can do after
Build it from scratch by creating a GitHub repository, committing local files, and pushing them to a remote.

Read how Build Python Web Apps with Streamlit explains repository →

Shipping Go: Develop, deliver, discuss, design, and go again

A managed storage location for source code and its associated history and development metadata.

How it is used
Anchors source code and pipeline work so teams can build, test, deploy, and share incremental product changes.
How deep it goes
Explains repository purpose, GitHub setup, local connection, and pipeline role without descending into version-control internals.
Examples
Uses a hello API README, GitHub setup, Git remote commands, and a Go-oriented .gitignore file.
What you can do after
Operate/configure a GitHub repository, connect a local project, and organize code for automated build, test, and deployment work.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains repository →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A code repository is a storage location that contains a software project's source code and related development history.

How it is used
Supports obtaining, modifying, and deploying example or microservice code through GitHub and Git.
How deep it goes
Defines repositories operationally through cloning, downloading, forking, workflow triggers, and splitting; preserves history as an advanced option.
Examples
Uses chapter repositories, separately forkable deployment examples, microservice repositories, and a Terraform infrastructure repository.
What you can do after
Operate/configure repositories by cloning local copies, forking them, enabling workflows, and separating microservice code.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains repository →

Kubernetes for Developers

A Git repository is a data store containing versioned files and the history of changes made to them.

How it is used
Organizes Kubernetes configuration for reviewable, Git-driven deployment.
How deep it goes
Explains namespace mappings, deployment triggers, and reconciliation, but only sketches continuous delivery beyond these mechanisms.
Examples
Uses namespace folders, kubectl apply -f ., Cloud Build triggers, and a cloudbuild-deploy.yaml deployment file.
What you can do after
Operate/configure Kubernetes environments by committing repository changes and triggering or reconciling deployments.

Read how Kubernetes for Developers explains repository →

100 SQL Server Mistakes and How to Avoid Them

A repository is a version-controlled storage area containing a project's files and their revision history.

How it is used
Protects project code from loss while coordinating parallel development and controlled merging.
How deep it goes
Explains repository setup, configuration, branching, conflicts, history, and rollback without detailing Git internals.
Examples
Uses MagicChoc’s unrecoverable development-server code and a Visual Studio SQL Server Database project.
What you can do after
Operate/configure a GitHub repository, create branches, manage conflicts, review changes, and roll back buggy code.

Read how 100 SQL Server Mistakes and How to Avoid Them explains repository →

Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools

A repository is a structured storage location containing a project's files and their associated version-control history.

How it is used
Uses repositories to manage PowerShell project files and their source-control history.
How deep it goes
Explains initialization, repository roots, branches, hidden metadata, and tracked status, then stops short of Git internals.
Examples
Demonstrates a MyPSTool folder, PowerShell files, git init, git status, GitHub remotes, and cloning a SharePoint tools repository.
What you can do after
Operate/configure a local Git repository, inspect its status, and connect it to a GitHub remote.

Read how Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools explains repository →

Practical Automation with PowerShell: Effective scripting from the console to the cloud

A GitHub repository is a version-controlled project storage space hosted on GitHub.

How it is used
Stores and shares a PowerShell module among team members while supporting an ongoing development workflow.
How deep it goes
Explains initialization, commits, remotes, pushes, access, branching, and pull requests, while deferring automated testing and code reviews.
Examples
Uses a PoshAutomator module, main and develop branches, commits, remote synchronization, collaborator settings, and a pull request.
What you can do after
Operate/configure a repository by initializing it, committing files, connecting GitHub, managing access, and proposing branch changes.

Read how Practical Automation with PowerShell: Effective scripting from the console to the cloud explains repository →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.