| commit | 501b5cbd4441c1262c001048852e201c09b8cb71 | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Wed May 27 15:23:06 2020 +0200 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu May 28 19:38:21 2020 +0000 |
| tree | b734c17555bf0e8340b8fb252e38c622eb0664fe | |
| parent | b3c53b7312b8bebcdda9a5560d7f5b6d187bd800 [diff] |
Remove .empty file Empty file was in place to allow committing the empty plugins directory. This cause noise in the logs since Gerrit tries to load the .empty file as if it was a plugin. Removed it and left to the Makefile the creation of the directory. Change-Id: I12741f1738e3db20bc86527c41a7bc5bd5663c7c
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.