91d3857341
* Update README * [Universe] Dark mode (#16545) * Dark mode updates (#16696) * [Universe] Corporate sponsors (#16457) * Dependency review beta (#16563) * Add placeholder topic file * Revert change I didn't make I'm not sure where this change came from or why it's showing up in my PR here but I didn't make this change and it's not part of Dependency Review so I'm reverting it. * Un-revert previous change OK I see what happened there. I was comparing the PR to main rather than the Universe megabranch, hence it showed a change I didn't make. This commit undoes the change I do not want to revert on the megabranch. * Update image to add the Checks tab * Finish updating topic to mention DR * Fix check errors * Fix another versioning error * Add a sentence about supported ecosystems * Add review changes * Remove Further reading topics in same category As suggested by James, I've removed the links to topics that are in the same `/collaborating-with-issues-and-pull-requests/` category as this topic. * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md * Updates in the light of Maya's review * Remove use of "exploit" in description * Change 'dependency review summary' to 'dependency review' See PR review comment from Maya. * Mention that the age of the dependency is given * Update screenshots to latest GUI * Add details of dependency ordering within a DR * Update content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * [Universe 2020] New audit log REST API endpoint (#16699) * Minimal updates for preview * ✨ API previews ✨ * Update beta note * ✨ Update API previews ✨ * ✨ Update previews ✨ * Add draft section for git events * Clean API previews * More fixes + API previews * Address review comments + update API previews * Mention cursor-based pagination * Update content/rest/overview/resources-in-the-rest-api.md Co-authored-by: Jeff Saracco <jeffsaracco@github.com> * Temporarily revert API previews * Small tweaks from review comments + API previews * revert json schemas * Updating OpenAPI descriptions (#16776) * Updating OpenAPI descriptions * Add decorated OpenAPI schema files Co-authored-by: Jeff Saracco <jeffsaracco@github.com> Co-authored-by: skedwards88 <skedwards88@github.com> Co-authored-by: github-openapi-bot <69533958+github-openapi-bot@users.noreply.github.com> * [Universe 2020] GitHub Actions: Workflow visualization (#16629) * initial empty commit * replace image used only for dotcom * add new image and version usage * add new image and version usage * add new image and version usage * add new image and version usage, delete unneeded image * add new image and version usage, fix incorrect image * add new image and version usage * add new image and version usage * add new image and version usage * add new image and version usage * update screenshot update * add new image and version usage * add new image and version usage * update text * update images and fix list numbering * add step with graph * Add missing versioning * add overview of visualization * fix title to match filename * add beta note * update wording * Restructuring packages (#16731) * restructuring packages * moving more content * moving more content * fixing the toc for guides * removing CR from the landing page * adjusting qs * updating npm * enhancing guides * Update updating-github-insights.md * fixing link problems * fixing link problems * redirecting the redirects * another change * fixing the guides landing page * add packages quickstart * moving CR content * adding some descriptive text * add packages landing page * adding guide content back * update popular articles based on data * fix caps on product name * try removing product from front matter * Update content/packages/quickstart.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/quickstart.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * add node package instructions to quickstart * fixing links and adding redirect * fixing redirects * renaming to container guides * renaming to container guides and fixing reusables * adding context and about section to CR * removign landign page extra titles and descriptions * reverting the packages * updating link * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * updating * update test to reflect redesigned product landing page * Add private vs public clarification * Fix borked test * filter out standalone category files from test Co-authored-by: Cynthia Rich <crichID@github.com> Co-authored-by: Cynthia Rich <crichID@users.noreply.github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Jason Etcovitch <jasonetco@github.com> * Add discussions video See https://github.com/github/docs-internal/pull/16759 * Remove typos * update article name in test Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: hubwriter <hubwriter@github.com> Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com> Co-authored-by: Jeff Saracco <jeffsaracco@github.com> Co-authored-by: skedwards88 <skedwards88@github.com> Co-authored-by: github-openapi-bot <69533958+github-openapi-bot@users.noreply.github.com> Co-authored-by: Meg Bird <megbird@github.com> Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> Co-authored-by: Cynthia Rich <crichID@github.com> Co-authored-by: Cynthia Rich <crichID@users.noreply.github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Jason Etcovitch <jasonetco@github.com>
2.3 KiB
2.3 KiB
title, intro, product, redirect_from, versions
| title | intro | product | redirect_from | versions | |||||
|---|---|---|---|---|---|---|---|---|---|
| Core concepts for GitHub Packages | Below is a list of common {% data variables.product.prodname_registry %} terms we use across our sites and documentation. | {% data reusables.gated-features.packages %} |
|
|
{% data reusables.package_registry.packages-ghes-release-stage %}
Package
A package is a self-contained and reusable piece of software that includes code and metadata that a developer bundles together in a common place for others to use. A package's metadata may include the version number, name, and the code's dependencies. Packages simplify using and distributing solutions to common problems such as needing frameworks for developing or testing a project, linters to improve code quality, or industry-standard machine learning tools to power your application. Packages exist in many ecosystems. For example, you can package Node.js and Java code or container images.
Container
A container is a unit of software designed to reliably deploy software in a standardized way on any platform. A container operates as an isolated virtual environment or instance that can run various software packages and components on the same host kernel as your operating system. Containers use fewer resources than virtual machines because they don't need to include their own virtual hardware to run. Containers are created using a container image file, such as a Dockerfile, and a container client or runtime program.
Container image
A container image is a type of package archive that specifies the software requirements to run an app from a container. A container image typically includes the app's code, libraries, and runtime instructions. To ensure that the same image details are used wherever an image is deployed and run, a container image is automatically versioned and cannot be changed once a container image is built in a container.
Docker container
A Docker container is a type of open source container built on the Docker platform. Docker's original image format has become the OCI (Open Container Initiative) Image Specification. For more information, see the "Docker documentation."