Comprehensive repository covering the installation and setup of essential DevOps and DevSecOps tools

Ansible delivers simple IT automation that ends repetitive tasks and frees up DevOps teams for more strategic work. This project is to enable this automation for NSX-T installation.

A collection of specialized TRAE Agents for software development, frontend, backend, automation, UI/UX, SEO, and DevOps. Each agent is ready to generate code, templates, scripts, and advanced workflows. Direct installation links included.

Automate the installation/uninstallation of essential DevOps tools on Linux and Windows with a single script. Perfect for DevOps engineers and enthusiasts looking to streamline their setup process.

No description available

DevToolBox is an open-source repository that provides a collection of installation, update, removal, and configuration scripts for a set of tools, software, and packages useful for developers, DevOps, and system administrators.

This Repository has the collection of knowledge documents on AWS, DevOps Tools and their Architecture, Installation and Project implementation, and deployments procedure.

# Git Credential Manager [](https://github.com/GitCredentialManager/git-credential-manager/actions/workflows/continuous-integration.yml) --- [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is a secure Git credential helper built on [.NET](https://dotnet.microsoft.com) that runs on Windows, macOS, and Linux. Compared to Git's [built-in credential helpers]((https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage)) (Windows: wincred, macOS: osxkeychain, Linux: gnome-keyring/libsecret) which provides single-factor authentication support working on any HTTP-enabled Git repository, GCM provides multi-factor authentication support for [Azure DevOps](https://dev.azure.com/), Azure DevOps Server (formerly Team Foundation Server), GitHub, Bitbucket, and GitLab. Git Credential Manager (GCM) replaces the .NET Framework-based [Git Credential Manager for Windows](https://github.com/microsoft/Git-Credential-Manager-for-Windows) (GCM), and the Java-based [Git Credential Manager for Mac and Linux](https://github.com/microsoft/Git-Credential-Manager-for-Mac-and-Linux) (Java GCM), providing a consistent authentication experience across all platforms. ## Current status Git Credential Manager is currently available for Windows, macOS, and Linux\*. GCM only works with HTTP(S) remotes; you can still use Git with SSH: - [Azure DevOps SSH](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops) - [GitHub SSH](https://help.github.com/en/articles/connecting-to-github-with-ssh) - [Bitbucket SSH](https://confluence.atlassian.com/bitbucket/ssh-keys-935365775.html) Feature|Windows|macOS|Linux -|:-:|:-:|:-: Installer/uninstaller|&#10003;|&#10003;|&#10003;\* Secure platform credential storage|&#10003; [(see more)](docs/credstores.md)|&#10003; [(see more)](docs/credstores.md)|&#10003; [(see more)](docs/credstores.md) Multi-factor authentication support for Azure DevOps|&#10003;|&#10003;|&#10003; Two-factor authentication support for GitHub|&#10003;|&#10003;|&#10003; Two-factor authentication support for Bitbucket|&#10003;|&#10003;|&#10003; Two-factor authentication support for GitLab|&#10003;|&#10003;|&#10003; Windows Integrated Authentication (NTLM/Kerberos) support|&#10003;|_N/A_|_N/A_ Basic HTTP authentication support|&#10003;|&#10003;|&#10003; Proxy support|&#10003;|&#10003;|&#10003; `amd64` support|&#10003;|&#10003;|&#10003; `x86` support|&#10003;|_N/A_|&#10007; `arm64` support|best effort|via Rosetta 2|best effort, no packages `armhf` support|_N/A_|_N/A_|best effort, no packages (\*) GCM guarantees support for the below Linux distributions. GCM maintainers also monitor and evaluate issues opened against other distributions to determine community interest/engagement and whether an emerging platform should become fully-supported. - Debian/Ubuntu/Linux Mint - Fedora/CentOS/RHEL - Alpine ## Download and Install ### macOS Homebrew The preferred installation mechanism is using Homebrew; we offer a Cask in our custom Tap. To install, run the following: ```shell brew tap microsoft/git brew install --cask git-credential-manager-core ``` After installing you can stay up-to-date with new releases by running: ```shell brew upgrade git-credential-manager-core ``` #### Git Credential Manager for Mac and Linux (Java-based GCM) If you have an existing installation of the 'Java GCM' on macOS and you have installed this using Homebrew, this installation will be unlinked (`brew unlink git-credential-manager`) when GCM is installed. #### Uninstall To uninstall, run the following: ```shell brew uninstall --cask git-credential-manager-core ``` --- ### macOS Package We also provide a [.pkg installer](https://github.com/GitCredentialManager/git-credential-manager/releases/latest) with each release. To install, double-click the installation package and follow the instructions presented. #### Uninstall To uninstall, run the following: ```shell sudo /usr/local/share/gcm-core/uninstall.sh ``` --- <!-- this explicit anchor should stay stable so that external docs can link here --> <!-- markdownlint-disable-next-line no-inline-html --> <a name="linux-install-instructions"></a> ### Linux #### Experimental: install from source helper script If you would like to help dogfood our new install from source helper script, run the following: 1. To ensure `curl` is installed: ```shell curl --version ``` If `curl` is not installed, please use your distribution's package manager to install it. 1. To download and run the script: ```shell curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh && sh ./install-from-source.sh && git-credential-manager-core configure ``` **Note:** You will be prompted to enter your credentials so that the script can download GCM's dependencies using your distribution's package manager. #### Ubuntu/Debian distributions Download the latest [.deb package](https://github.com/GitCredentialManager/git-credential-manager/releases/latest), and run the following: ```shell sudo dpkg -i <path-to-package> git-credential-manager-core configure ``` **Note:** Although packages were previously offered on certain [Microsoft Ubuntu package feeds](https://packages.microsoft.com/repos/), GCM no longer publishes to these repositories. Please install the Debian package using the above instructions instead. To uninstall: ```shell git-credential-manager-core unconfigure sudo dpkg -r gcmcore ``` #### Other distributions Download the latest [tarball](https://github.com/GitCredentialManager/git-credential-manager/releases/latest), and run the following: ```shell tar -xvf <path-to-tarball> -C /usr/local/bin git-credential-manager-core configure ``` To uninstall: ```shell git-credential-manager-core unconfigure rm $(command -v git-credential-manager-core) ``` **Note:** all Linux distributions [require additional configuration](https://aka.ms/gcm/credstores) to use GCM. --- ### Windows GCM is included with [Git for Windows](https://gitforwindows.org/), and the latest version is included in each new Git for Windows release. This is the preferred way to install GCM on Windows. During installation you will be asked to select a credential helper, with GCM being set as the default.  #### Standalone installation You can also download the [latest installer](https://github.com/GitCredentialManager/git-credential-manager/releases/latest) for Windows to install GCM standalone. **:warning: Important :warning:** Installing GCM as a standalone package on Windows will forcibly override the version of GCM that is bundled with Git for Windows, **even if the version bundled with Git for Windows is a later version**. There are two flavors of standalone installation on Windows: - User (preferred) (`gcmcoreuser-win*`): Does not require administrator rights. Will install only for the current user and updates only the current user's Git configuration. - System (`gcmcore-win*`): Requires administrator rights. Will install for all users on the system and update the system-wide Git configuration. To install, double-click the desired installation package and follow the instructions presented. #### Uninstall (Windows 10) To uninstall, open the Settings app and navigate to the Apps section. Select "Git Credential Manager" and click "Uninstall". #### Uninstall (Windows 7-8.1) To uninstall, open Control Panel and navigate to the Programs and Features screen. Select "Git Credential Manager" and click "Remove". #### Windows Subsystem for Linux (WSL) Git Credential Manager can be used with the [Windows Subsystem for Linux (WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git repositories from inside of WSL. [Please see the GCM on WSL docs](docs/wsl.md) for more information. ## Supported Git versions Git Credential Manager tries to be compatible with the broadest set of Git versions (within reason). However there are some know problematic releases of Git that are not compatible. - Git 1.x The initial major version of Git is not supported or tested with GCM. - Git 2.26.2 This version of Git introduced a breaking change with parsing credential configuration that GCM relies on. This issue was fixed in commit [`12294990`](https://github.com/git/git/commit/12294990c90e043862be9eb7eb22c3784b526340) of the Git project, and released in Git 2.27.0. ## How to use Once it's installed and configured, Git Credential Manager is called implicitly by Git. You don't have to do anything special, and GCM isn't intended to be called directly by the user. For example, when pushing (`git push`) to [Azure DevOps](https://dev.azure.com), [Bitbucket](https://bitbucket.org), or [GitHub](https://github.com), a window will automatically open and walk you through the sign-in process. (This process will look slightly different for each Git host, and even in some cases, whether you've connected to an on-premises or cloud-hosted Git host.) Later Git commands in the same repository will re-use existing credentials or tokens that GCM has stored for as long as they're valid. Read full command line usage [here](docs/usage.md). ### Configuring a proxy See detailed information [here](https://aka.ms/gcm/httpproxy). ## Additional Resources - [Frequently asked questions](docs/faq.md) - [Development and debugging](docs/development.md) - [Command-line usage](docs/usage.md) - [Configuration options](docs/configuration.md) - [Environment variables](docs/environment.md) - [Enterprise configuration](docs/enterprise-config.md) - [Network and HTTP configuration](docs/netconfig.md) - [Credential stores](docs/credstores.md) - [Architectural overview](docs/architecture.md) - [Host provider specification](docs/hostprovider.md) - [Azure Repos OAuth tokens](docs/azrepos-users-and-tokens.md) - [GitLab support](docs/gitlab.md) ## Experimental Features - [Windows broker (experimental)](docs/windows-broker.md) ## Contributing This project welcomes contributions and suggestions. See the [contributing guide](CONTRIBUTING.md) to get started. This project follows [GitHub's Open Source Code of Conduct](CODE_OF_CONDUCT.md). ## License We're [MIT](LICENSE) licensed. When using GitHub logos, please be sure to follow the [GitHub logo guidelines](https://github.com/logos).

This Repository consists of DevOps tools installation

A Big Data Analytics VM for doing Data Science. It provides a huge kickstart to those working with the Big Data Analytics side of Data Science. Essentially, this project automates the creation of the Big Data Scientist's toolbox on a virtual machine (VM). In a few minutes one can begin working with a fully configured data science lab instead of performing the complex installations and configuration required for a functioning development environment. The Data Scientist's VM includes R, Git, Python, Cloudera, Hadoop, YARN, MRv2, Mahout, MongoDB, Spark, Neo4j, etc. pre-installed. The Data Scientist's Toolbox VM is automatically built for you on a single CentOS VM using the Vagrant DevOps tool with Chef and shell-scripts for VMware Fusion.

My installation guides and bash script for essential DevOps tools like Jenkins (CI/CD), Nexus (artifact repository), SonarQube (code analysis), Docker (containerization), and Trivy (vulnerability scanning) on Server like EC2.

SUPERLAMP is a Bash TUI for Debian/Ubuntu that automates the installation and management of a complete LAMP+FM+DevOps stack: Apache2, MySQL/MariaDB, PHP+phpMyAdmin, FTP, Python, Git, Node.js with Composer/NVM, Docker, UFW, Fail2Ban and SSL. Includes smart updates, service control, DB wizard, site scaffolding, dry-run and verbose modes.

Get your lab! Automatic installation of a DevOps Lab

🤖 Professional AI specialist agents for Claude Code CLI - curated from industry-leading AI tools. 12 specialized agents covering backend, frontend, DevOps, security, management & more. Plug-and-play installation.

(MOVED: https://github.com/openemr/openemr-devops) A production grade solution for facilities and hospitals to run their OpenEMR v5 installation in the cloud.

A framework designed to streamline third-party software installation and configuration. It is designed to make endpoint managers more agile with a Configuration Management, DevOps, and Infrastructure as Code (IaC) mentality.

A comprehensive guide to installing and configuring essential DevOps tools like Docker, Jenkins, Prometheus, Grafana, Helm, and more on Ubuntu/Linux, with step-by-step instructions for beginners and professionals.

Master DevOps Tools Installation & Configuration — Your comprehensive guide to setting up a professional DevOps environment with step-by-step tutorials and best practices.

A Guide for Installing Devops tools. This should be helpful when you are switching to a new PC

Grafana + Prometheus Installation on Ubuntu (Beginner-friendly Guide) - Perfect Monitoring Stack for DevOps Engineers

The DevOps Tools Installation Guide repository provides an automated solution to set up a comprehensive suite of essential DevOps tools on Linux systems using Ansible. 🛠️💻🔧

Python script automates the installation of various DevOps tools

setup-server-automate is an automation project designed to streamline the setup of a DevOps environment on a server. It includes a series of scripts that automate the installation and configuration of essential software and services, making it easier to establish a robust and secure development and production environment.

🚀 A complete Jenkins Zero-to-Hero learning project covering installation, master–agent setup, CI/CD pipelines, Docker integration, notifications, user management, backups, upgrades, and real-world build pipelines for Node.js, Angular, Maven, and Gradle. This project helps beginners and DevOps engineers master Jenkins with hands-on examples

DevOps Tools Installation guide

Bash For Basic DevOps in Ubuntu Installation

Jenkins is an open source, Java-based automation server that offers an easy way to set up a continuous integration and continuous delivery (CI/CD) pipeline. Continuous integration (CI) is a DevOps practice in which team members regularly commits their code changes to the version control repository, after which automated builds and tests are run. Continuous delivery (CD) is a series of practices where code changes are automatically built, tested and deployed to production. This tutorial will walk you through the steps of installing Jenkins on a CentOS 7 system using the official Jenkins repository. Prerequisites Before continuing with this tutorial, make sure you are logged in as a user with sudo privileges. Installing Jenkins To install Jenkins on your CentOS system, follow the steps below: Jenkins is a Java application, so the first step is to install Java. Run the following command to install the OpenJDK 8 package: sudo yum install java-1.8.0-openjdk-devel Copy The current version of Jenkins does not support Java 10 (and Java 11) yet. If you have multiple versions of Java installed on your machine make sure Java 8 is the default Java version. The next step is to enable the Jenkins repository. To do that, import the GPG key using the following curl command: curl --silent --location http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo | sudo tee /etc/yum.repos.d/jenkins.repo Copy And add the repository to your system with: sudo rpm --import https://jenkins-ci.org/redhat/jenkins-ci.org.key Copy Once the repository is enabled, install the latest stable version of Jenkins by typing: sudo yum install jenkins Copy After the installation process is completed, start the Jenkins service with: sudo systemctl start jenkins Copy To check whether it started successfully run: systemctl status jenkins Copy You should see something similar to this: ● jenkins.service - LSB: Jenkins Automation Server Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled) Active: active (running) since Thu 2018-09-20 14:58:21 UTC; 15s ago Docs: man:systemd-sysv-generator(8) Process: 2367 ExecStart=/etc/rc.d/init.d/jenkins start (code=exited, status=0/SUCCESS) CGroup: /system.slice/jenkins.service Copy Finally enable the Jenkins service to start on system boot. sudo systemctl enable jenkins Copy jenkins.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig jenkins on Copy Adjust the Firewall If you are installing Jenkins on a remote CentOS server that is protected by a firewall you need to port 8080. Use the following commands to open the necessary port: sudo firewall-cmd --permanent --zone=public --add-port=8080/tcp sudo firewall-cmd --reload Copy Setting Up Jenkins To setup your new Jenkins installation, open your browser and type your domain or IP address followed by port 8080: http://your_ip_or_domain:8080 Copy A screen similar to the following will appear, prompting you to enter the Administrator password that is created during the installation: Use the following command to print the password on your terminal: sudo cat /var/lib/jenkins/secrets/initialAdminPassword Copy You should see a 32-character long alphanumeric password as shown below: 2115173b548f4e99a203ee99a8732a32 Copy Copy the password from your terminal, paste it into the Administrator password field and click Continue. On the next screen you will be asked whether you want to install the suggested plugins or to select specific plugins. Click on the Install suggested plugins box, and the installation process will start immediately. Once the installation is complete, you will be prompted to set up the first administrative user. Fill out all required information and click Save and Continue. On the next page you will be asked to set the URL for the Jenkins instance. The URL filed will be populated with an automatically generated URL. To complete the setup confirm the URL by clicking on the Save and Finish button. Finally, click on the Start using Jenkins button and you will be redirected to the Jenkins dashboard logged in as the admin user you have created in one of the previous steps. If you’ve reached this point, you’ve successfully installed Jenkins on your CentOS system. Conclusion In this tutorial, you have learned how to install and complete the initial configuration of Jenkins on CentOS/RHEL based systems. You can now visit the official Jenkins documentation page and start exploring Jenkins’s workflow and plug-in model.

No description available

This repository serves as a collection of important installation steps and notes for various DevOps practices.

No description available