fix
patch
fix/deploy-memory-limits-and-log-group
#1 / 1
fix: raise app/worker container memory limits, fix hardcoded staging log group
Found while pushing muse's full history to production: /push/unpack-mpack processes an entire mpack synchronously in memory, and the app container's 2GiB limit (and postgres's 256MiB) OOM'd under a ~389MB/11K-object payload, confirmed via dmesg OOM-killer entries.
- deploy.sh: raise app/worker container memory to 3GiB (APP_MEMORY_LIMIT), fix awslogs-group hardcoded to /musehub/staging for both environments - push.sh: export MUSEHUB_ENV so deploy.sh knows which log group to use - docs/infrastructure.md: document the new limits, the live (unscripted) postgres bump to 1GiB, and link the follow-up for the real fix (#170 on staging: make unpack-mpack asynchronous)
sha256:b3d08ea378601022e598a698496dcbec8b699d379bacb956a9b640fb99bcc35c
sha
+5
~8
symbols
3 changed · 1060 in snapshot
files
sha256:5be7e1201431c06bb174d7269a90da220d97c9a452b58d04efbdb68f81c624a2
snapshot
+5
symbols added
~8
symbols modified
3
files changed
1060
files in snapshot
0
dead code introduced
Semantic Changes
13 symbols
+
.vscode/
+
alembic/
+
deploy/
+
docs/
+
musehub/
+
scripts/
+
src/
+
src/ts/
+
tests/
+
tools/
Files Changed
~3
1060 in snapshot
~3
1060 in snapshot
← Older
Oldest on fix/deploy-memory-limits-and-log-group
All commits
Newer →
Latest on fix/deploy-memory-limits-and-log-group
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:b3d08ea378601022e598a698496dcbec8b699d379bacb956a9b640fb99bcc35c --body "your comment"
No comments yet. Be the first to start the discussion.