|author||Antonio Barone <email@example.com>||Tue Oct 20 17:53:56 2020 +0200|
|committer||Luca Milanesio <firstname.lastname@example.org>||Wed Nov 04 08:56:55 2020 +0000|
Use git config to set password in secure.config Storing password strings directly by substituting placeholders into the secure.config template was causing issues whereby special characters were not escaped correctly. To circumvent this, the user was asked to do the relevant escaping before setting the password strings. Use git config to set passwords in order to delegate the responsibility of proper escaping to the git tool rather the admin user. Bug: Issue 13186 Change-Id: I88e543bc92d6dd8dd07ff032f4d7bc4fa0e40371
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.
To build gerrit and related-components' images Docker
This is a list of external services that you might need to setup your stack and some suggestions on how to easily create them.
If you need to setup a SMTP service Amazon Simple Email Service can be used. Details how setup Amazon SES can be found here.
To correctly setup email notifications Gerrit requires ssl protocol on default port 465 to be enabled on SMTP Server. It is possible to setup Gerrit to talk to standard SMTP port 25 but by default all EC2 instances are blocking it. To enable port 25 please follow this link.
If you need a testing LDAP server you can find details on how to easily create one in the LDAP folder.