commit | 794862faaba35cd0db630e6736eb38c7e330b23f | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 21:37:54 2020 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 20:38:28 2020 +0000 |
tree | 50c4a69ed3682c762c98c5305b0bd3606f6c9a30 | |
parent | 0178c31c1c483586089750575cfe522ebc08c17f [diff] |
Base all image paths on the project ROOT_DIR Calculate the ROOT_DIR of the project by looking for the Makefile.common in the whole list of Makefiles included and get its absolute path name. Then reuse this variables, instead of relative paths, for assuring that all images are calculating their positions and SHA1s in a consistent way. Change-Id: I527fc5d42bd7d27f90c8b7eca70793e687d2048e
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.