| commit | 5fab0e4c48319e4f80fe59803cbc91223a27b38d | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 21 02:02:44 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 21 12:22:55 2020 +0100 |
| tree | 7e40d43e565b0cb01b6254ef474d37161e2783d6 | |
| parent | a309ad51830a1118728a0c94f6ac75d53b803570 [diff] |
Fix master-slave recipe Fix many breakages on the master-slave recipe: - generation of the Prometheus bearer token - sequence of resolution of variables - reference to the Gerrit slave docker image - service discovery of git-daemon - missing includes in the git-ssh and git-daemon Makefiles - missing GERRIT_KEY_PREFIX in git-ssh container's setup - fix replication.config.template with more suitable sample values - fix sequence of activation of the master-slave services This change breaks the rule "one change = one thing", however, here the thing is really "making master-slave recipe work". Change-Id: Ic71ab16a4e83de60b4b2877727ad71abd79f117c
Those are a collection of AWS CloudFormation templates and scripts to deploy Gerrit in AWS.
The aim is to provide some guidelines and example on how to deploy different Gerrit setups in the Cloud using AWS as provider.
The goal of Gerrit AWS Templates is to provide fully-functional Gerrit installations to helps users deploying Gerrit on AWS by providing out-of-the-box templates.
With Gerrit AWS Templates, developers and administrator can create a production-ready installation on the cloud in minutes and in a repeatable way, allowing them to focus on fine tuning of the Gerrit configuration to suit the user needs.
The provided CloudFormation templates automate the entire creation and deployment of the infrastructure and the application.
To manage your AWS services via command line you will need to install AWS CLI and set it up to point to your account.