Skip to content

Commit

Permalink
(chocolatey#970) Add considerations for cleanup policy, authenticatio…
Browse files Browse the repository at this point in the history
…n, and blob stores

This commit adds information into the Nexus installation portion of the new Organizational deployment guide
which covers cleanup policy with included link to Nexus documentation, authentication with link to Nexus
documentation, and blob stores with included link to Nexus documentation.
  • Loading branch information
steviecoaster committed Mar 15, 2024
1 parent 1ac154c commit f5ad4b9
Showing 1 changed file with 18 additions and 2 deletions.
20 changes: 18 additions & 2 deletions input/en-us/guides/organizations/new-org-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,22 @@

#### Authentication Considerations

#### Package Clean-up Policies
Authenticating to a repository hosted in Sonatype Nexus via the Chocolatey client should follow the security requirements of your organization. For some organizations, the clients communicate on internal networks, and have no egress so having anonymous authentication to the repository is deemed acceptable.

#### Package Storage Requirements (Blob Stores)
Sonatype Nexus supports local user authentication and LDAP autentication in the Open Source version, and supports User Token based authentication in their paid Nexus Repository Pro offering. Chocolatey CLI Supports all of these scenarios.

#### Package Cleanup Policies

Cleanup Policies are used in Sonatype Nexus to keep the number of stored components in your repositories at a level that helps maintain
the stability of your server. When left unchecked repositories become unperformant when a large number of components are stored inside the repository. This impacts things such as search and disk space.

We recommend you keep _at least_ N+2 versions of packages in your repository, as Chocolatey has a very easy to use downgrade procedure should the latest version of a package cause inconsistent behavior anywhere in your organization. To configure a Cleanup Policy, consult the [documentation](httpsa://ch0.co/nexus-cleanup-policy) on Sonatype's website.

>
> :warning: Be sure to follow the documentation to configure the [Compact Blob Store](https://ch0.co/nexus-tasks) task, as Cleanup Policies
>by default perform a soft delete, keeping any data on disk until the `Compact Blob Store` task is executed.
>
#### Package Storage Requirements (Blob Stores)

Sonatype Nexus stores packages in what it calls a Blob Store. When you upload a package to the repository, Nexus indexes this file into the blob store as a binary representation of the file. For a standard Chocolatey installation we recommend you start with 500GB of disk space for your Blob store. To configure the blob store for your organization, consult the [documentation](https://ch0.co/nexus-blobs) on Sonatype's website. For information on setting up the authentication your organization requires see the [documentation](https://ch0.co/nexus-authentication) for information and instructions.

0 comments on commit f5ad4b9

Please sign in to comment.