https://github.com/cloudreach/sceptre-wordpress-example
sceptre wordpress configured HA mode in AWS
https://github.com/cloudreach/sceptre-wordpress-example
aws cloud cloudformation devops efs sceptre troposphere wordpress
Last synced: 20 days ago
JSON representation
sceptre wordpress configured HA mode in AWS
- Host: GitHub
- URL: https://github.com/cloudreach/sceptre-wordpress-example
- Owner: cloudreach
- License: other
- Created: 2017-04-10T11:45:31.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2021-08-11T08:48:27.000Z (over 4 years ago)
- Last Synced: 2024-04-21T17:23:27.858Z (almost 2 years ago)
- Topics: aws, cloud, cloudformation, devops, efs, sceptre, troposphere, wordpress
- Language: Python
- Size: 106 KB
- Stars: 10
- Watchers: 16
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
- License: LICENSE
Awesome Lists containing this project
README
=======
Sceptre Wordpress
=======
Meetup Munich
-----
Sceptre is a tool to drive AWS `CloudFormation `_. It automates away some of the more mundane, repetitive and error-prone tasks, allowing you to concentrate on building better infrastructure.
Sceptre's source code can be found `here `_.
Features:
- Code reusability by separating a stack's template and its configuration
- Support for templates written in JSON, YAML or Python DSLs such as Troposphere
- Dependency resolution by passing of stack outputs to parameters of dependent stacks
- Environment support by bundling related stacks into logical groups (e.g. dev and prod)
- Environment-level commands, such as creating multiple stacks with a single command
- Fast, highly parallelised builds
- Built in support for working with stacks in multiple AWS accounts
- Infrastructure visibility with meta-operations such as stack querying protection
- Support for inserting dynamic values in templates via customisable resolvers
- Support for running arbitrary code as hooks before/after stack builds
Code
-------
Sceptre organises stacks into environments. Each stack is represented by a YAML configuration file stored in a directory which represents the environment. Here, we have two environments, ``prod`` and ``dev`` ::
$ tree
.
├── LICENSE
├── NOTICE
├── README.rst
├── config
│ ├── config.yaml
│ ├── dev
│ │ ├── config.yaml
│ │ ├── efs.yaml
│ │ ├── rds.yaml
│ │ ├── role.yaml
│ │ ├── security-groups.yaml
│ │ ├── vpc.yaml
│ │ └── wordpress.yaml
│ └── prod
│ ├── config.yaml
│ ├── efs.yaml
│ ├── rds.yaml
│ ├── security-groups.yaml
│ ├── vpc.yaml
│ └── wordpress.yaml
└── src
├── base.py
├── constants.py
├── efs.py
├── rds.py
├── role.py
├── security_groups.py
├── vpc.py
└── wordpress.py
Diagram
-------
.. image:: diagram.jpg
:align: right
Install
-------
::
$ pip install sceptre
More information on installing sceptre can be found in our `Installation Guide `_.
How to start
-----
Sceptre can be used from the CLI, or imported as a Python package.::
$ git clone git@github.com:cloudreach/sceptre-wordpress-example.git
$ cd sceptre-wordpress-example
Be sure your `AWS credential `__ are properly configured
How to deploy ``dev`` and ``prod`` ::
$ sceptre launch dev
$ sceptre launch prod
How to apply a change-set on ``dev`` for ``wordpress`` stack ::
$ sceptre create dev wordpress
$ sceptre execute dev wordpress
Tutorial and Documentation
--------------------------
- `Get Started `_
- `Documentation `__
License
-------------
**sceptre** is licensed under the `Apache Software License 2.0 `_.
Thanks
-------------
`Intelligent Cloud Adoption. `_