| commit | 4e9715a105e52f39e4f35c518d9fb38799ba423b | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Tue Apr 07 11:50:47 2020 +0200 |
| committer | Fabio Ponciroli <ponch78@gmail.com> | Tue Apr 07 10:58:05 2020 +0000 |
| tree | 9e030a9184f55b76cc687337246e354bf7884acf | |
| parent | a8d593d860f1a72bde7f7163663677467cbc57b1 [diff] |
Simplify entrypoint Gerrit script Before this change the modification of the gerrit.config was happening in different places and there were several conditional statements. Now the logic is more linear: 1. Populate gerrit.config and secure.config 2. Init, if needed 3. Run Gerrit This refactoring will be particular useful later on when adding further logic to handle, for example, the different init phases of master and slave. Change-Id: I49e0e4c46e6aa73510dfb80bc763fdc288ddbecd Feature: Issue 12554
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.