-
Notifications
You must be signed in to change notification settings - Fork 166
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4530c00
commit 148bc0f
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# 'production' Empire example | ||
|
||
This is meant to be a base guideline for building a production ready | ||
[Empire][Empire] cluster. In order to launch it, you'll want to modify the | ||
[example.env][example.env] to fit your needs. It's worth reading through the | ||
[example.env][example.env] & [empire.yaml][empire.yaml] for the comments that | ||
detail how things will be built. Once the env is to your liking, you can launch | ||
the environment by running the following command: | ||
|
||
``` | ||
$ stacker -e conf/empire/example.env -r <region> <namespace> conf/empire/empire.yaml | ||
``` | ||
|
||
Right now it takes around 20-30 minutes to finish bringing up the entire | ||
environment due largely to how long it takes RDS to build the Empire database. | ||
|
||
Rather than use the ECS Container AMI that Amazon provides, the Empire team | ||
has built their own [Empire AMI][empire_ami] based on Ubuntu 14.04. | ||
|
||
[Empire]: https://github.com/remind101/empire/ | ||
[example.env]: https://github.com/remind101/stacker/blob/master/conf/empire/example.env | ||
[empire.yaml]: https://github.com/remind101/stacker/blob/master/conf/empire/empire.yaml | ||
[empire_ami]: https://github.com/remind101/empire_ami |