| commit | 03557a0e589bee836a989d59906da5c1bd91149c | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Thu May 28 16:23:37 2020 +0200 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 19:40:24 2020 +0000 |
| tree | 359d7cc9549f4a235ea40f2331a18dd183aa0e20 | |
| parent | 501b5cbd4441c1262c001048852e201c09b8cb71 [diff] |
Fix Gerrit root directory The common.env file is included from different Makefiles, depending on the target. Depending on the caller, MAKEFILE_LIST has different values, hence it is not possible to always get the last value to determine the Gerrit directory. The invocation will always happen for sure from a subdirectory of root. The '../gerrit' directory change will ensure the Gerrit directory value will be added to the root one. Change-Id: I62b85097007c45709419848a47802c35f8850a94
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.