Draft - Re-Work of Organization Deployment Guide

What New Or Updated Would You Like To See?

I'm creating this issue to template out the new design idea I have for an updated Organization Deployment Guide. This is meant to be a meta issue where subsequent other issues will spawn off of this one. It is mainly to keep track of all the proposed changes and additions in one nice to see spot within GitHub as this gets worked on.

I want the new Organizational Deployment Guide to have Docs for setting up Jenkins, Nexus, and CCM as discreet services apart from one another. Much like we do with our POC Chocolatey enviornment solutions such as QSG and the C4B Azure Enviornment. But piece mail, showing that you aren't constricted to just the tools we give in our enviornment offerings.

I mainly wanna focus this guide at catering to people that may have a config manager, and or repository solution already established in their organizations enviornment. Those that would just need to bolt on a CI/CD solution and Chocolatey to have a fully working C4B Enviornment as an example.

This also offers a great place to link off to expanded content for all the solutions we work with for each of the components. Here are examples:

Repository Solutions:

Sonotype Nexus
Inedo ProGet
JFrog Artifactory
Cloudsmith
etc.

CI/CD Tools:

Jenkins
TeamCity
GitHub Actions
Azure DevOps Pipelines
Circle CI
etc.

Deployment or Config Manager Solutions

CCM
Boxstarter
Ansible
Puppet
Chef
DSC
etc.

Full Solution Setup Provided for OSS Repository Offering

[ ] Create Nexus Setup Guide Doc. Can leverage the NexuShell Powershell Module. Call pull most of this from QSG repo.
[ ] Create Setting Up Nexus to Run over SSL Guide as recommended additional step, again making use of NexuShell Powershell Module. Can also pull most of this from QSG repo.
[ ] Create Working with Chocolatey and Nexus Doc, this will cover creating new repos, diving into how nexus does roles and permissions and relating that to Chocolatey source authentication. Also maybe covering topics such as setting up Nuget cleanup policies.

Repository Solution Docs and Videos

[ ] Create video accompaniment to Chocolatey and Nexus Doc, being used to later link video directly into doc as a video reference. Much like we do currently with the video at the end of the Quick Start Guide. This goes for all video tasks mentioned going forward.
[ ] Create Using Artifactory as your Chocolatey Repository Doc
[ ] Create video to go with Using Artifactory as your Chocolatey Repository Doc
[ ] Create Using ProGet as your Chocolatey Repository Doc
[ ] Create video to go with Using ProGet as your Chocolatey Repository Doc
[ ] Create Using Cloudsmith as your Chocolatey Repository
[ ] Create video to go with Using Cloudsmith as your Chocolatey Repository, can use https://www.youtube.com/watch?v=uM3K7aO9Sk0 as a template but make the one we use just Chocolatey focused.
[ ] Create Using ProGet as your Chocolatey Repository Doc
[ ] Create video to go with Using ProGet as your Chocolatey Repository Doc

Configuration Management Solutions

Look to create docs on installing C4B using the different config managers we support. We should have video content working with most of these guys already that we can link to in these docs.

Why Is It Needed?

Changes to the Organization Deployment Guide are needed as the Chocolatey product offering has evolved since it was originally written. It should more directly call out the Jenkins(CI/CD component) and CCM (package deployment mechanism) as parts of setting up a full C4B Enviornment.

chocolatey / docs