Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen findest Du in unserer englischsprachigen Dokumentation.
Deutsch
No results found.

Nach Produkt erkunden

Enterprise administrators
  • Get started
  • Account and profile
  • Authentication
  • Repositories
  • GitHub
  • Enterprise administrators
  • Billing and payments
  • Organizations
  • Code security
  • GitHub Issues
  • GitHub Actions
  • GitHub Codespaces
  • GitHub Packages
  • Search on GitHub
  • Developers
  • REST API
  • GraphQL API
  • GitHub CLI
  • GitHub Discussions
  • GitHub Sponsors
  • Building communities
  • GitHub Pages
  • Education
  • GitHub Desktop
  • Atom
  • Electron
  • CodeQL
  • npm
    • Deutsch
  • English
  • 简体中文 (Simplified Chinese)
  • 日本語 (Japanese)
  • Español (Spanish)
  • Português do Brasil (Portuguese)

    • Diese Version von GitHub Enterprise wurde eingestellt am 2021-09-23. Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für eine bessere Leistung, verbesserte Sicherheit und neue Features nimm ein Upgrade auf die neueste Version von GitHub Enterprise vor. Wende Dich an den GitHub Enterprise-Support, um Hilfe beim Upgrade zu erhalten.

    Artikelversion

    Inhalt dieses Artikels

    Getting started with GitHub Packages for your enterprise

    You can start using GitHub Packages on your GitHub Enterprise Server instance by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.

    Note: GitHub Packages is currently in beta for GitHub Enterprise Server 2.22. To join the beta for your GitHub Enterprise Server instance, use the sign-up form.

    Note: After you've been invited to join the beta, follow the instructions from your account representative to enable GitHub Packages for your GitHub Enterprise Server instance.

    Note: GitHub Packages on GitHub Enterprise Server does not currently support clustering.

    Step 1: Enable GitHub Packages and configure external storage

    GitHub Packages on GitHub Enterprise Server uses external blob storage to store your packages.

    After enabling GitHub Packages for your GitHub Enterprise Server instance, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of GitHub Packages, and the setup guidelines can vary by storage provider.

    Supported external storage providers

    • Amazon Web Services (AWS) S3
    • MinIO

    To enable GitHub Packages and configure third-party storage, see:

    Step 2: Specify the package ecosystems to support on your instance

    Choose which package ecosystems you'd like to enable, disable, or set to read-only on your GitHub Enterprise Server instance. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "Configuring package ecosystem support for your enterprise."

    Step 3: Ensure you have a TLS certificate for your package host URL, if needed

    If subdomain isolation is enabled for your GitHub Enterprise Server instance, which is required to use GitHub Packages with Docker, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as npm.HOSTNAME. Make sure each package host URL includes https://.

    You can create the certificate manually, or you can use Let's Encrypt. If you already use Let's Encrypt, you must request a new TLS certificate after enabling GitHub Packages. For more information about package host URLs, see "Enabling subdomain isolation." For more information about uploading TLS certificates to GitHub Enterprise Server, see "Configuring TLS."