https://github.com/johnweland/wordpress-cdk
https://github.com/johnweland/wordpress-cdk
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/johnweland/wordpress-cdk
- Owner: johnweland
- Created: 2023-05-03T17:57:31.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2023-05-03T20:32:44.000Z (almost 2 years ago)
- Last Synced: 2025-01-24T17:46:00.120Z (3 months ago)
- Language: TypeScript
- Size: 41 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# WordPress CDK
## Setup
To deploy the infrastructure, run the following commands:
```bash
cd cdk
```
```bash
npm install
```
## Usage
To deploy everything
```bash
cdk deploy --profile
```
To deploy a specific stack
```bash
cdk deploy --profile
```
Some stacks require parameters
```bash
cdk deploy --profile --parameters =
```
### Stacks
**SetupStack**: builds out long living requirements. For Example the ERC repository.
**WordpressStack**: builds out the wordpress application and its infrastructure dependencies. For Example: ECS, RDS, EFS, etc.
> _Note: The wordpress stack requires the setup stack to be deployed first._
## FAQ
> Q: Why separate stacks?
>
> A: It could be done so there is a single stack to deploy everything. However I feel that some resources are long living and should be deployed once and left alone. For example the ERC repository. This stack is meant to be deployed once and left alone. The wordpress stack is meant to be deployed multiple times (for multiple test branches within a single dev account). For example, if you want to deploy a new version of wordpress, you would deploy the wordpress stack again. This would create a new ECS task definition and update the ECS service to use the new task definition.