build: deployment updates. #157
Conversation
morganney
commented
Jan 5, 2024
•
morganney
commented
- Added Normalize the database initialization approach #159 to resolve keeping the two scripts in sync.
- Added Redis memory overcommit warning #160 as unfinished from 122
- Closes Docker build secrets #134
- Closes Deployment and Infrastructure #122
| @@ -1,6 +1,6 @@ | |||
| # DNS resolution works at startup via `depends_on` for `web` service in compose.yaml. | |||
| upstream api_server { | |||
| server api:3000; | |||
| server ${UPSTREAM_API_HOST}:3000; | |||
There was a problem hiding this comment.
In case I will use awsvpc network mode (which allows containers to communicate with localhost). This happens when running nginx as an aws copilot sidecar.
| VpcSecurityGroupIds: | ||
| - !Ref bmclusterDBClusterSecurityGroup | ||
| ServerlessV2ScalingConfiguration: | ||
| # Replace "All" below with "!Ref Env" to set different autoscaling limits per environment. |
There was a problem hiding this comment.
Notice, without following what this comment suggests then every environment is the DBMinCapacity and DBMaxCapacity defined for All. In this case 2 and 8 respectively.
For now, the test environment is more or less a staging for beta testing, UAT, etc., so it makes sense to have the same capacity expected for production.
If necessary I can set up environment level autoscaling when I need more than a staging environment, or other environments.
There was a problem hiding this comment.
Added #159 to resolve now having two initialization scripts to keep in sync.
