commit | 449c100440fac7acb8cc5ba7a4050db45be16b64 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 16:09:56 2020 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 20:40:51 2020 +0100 |
tree | e74d660e8092c2047cc63484e1af28ce3e23c5c0 | |
parent | 632fb357e92b8b4471c625392d30e0b5fe2b69c3 [diff] |
Add missing LB_SUBDOMAIN for dual-master config The dual-master receipe was missing the LB_SUBDOMAIN in the setup.env.template, making the service-lb stack to fail during creation. Change-Id: I87026cd6f709d24b3b461f5319cca0dedfd075a9
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.