Skip to content

fix(deploy): align API pool compose defaults with ADR 0020 Phase 1 - #294

Merged
kl3inIT merged 1 commit into
mainfrom
fix/api-pool-compose-default
Aug 4, 2026
Merged

fix(deploy): align API pool compose defaults with ADR 0020 Phase 1#294
kl3inIT merged 1 commit into
mainfrom
fix/api-pool-compose-default

Conversation

@kl3inIT

@kl3inIT kl3inIT commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

Completes the pool right-sizing shipped in #292. The production compose layer (infrastructure/deployment/compose.production.yaml) injects ORGMEMORY_API_DB_POOL_MAXIMUM_SIZE/MINIMUM_IDLE with compose-level defaults 12/2, which override the new application-prod.yml defaults of 8/8 — verified live on the zm host after the #292 deploy (container env still 12/2). This aligns the compose defaults (api + age-reconcile) with the decided 8/8. The host .env.production pins neither variable, so the compose default is authoritative.

skip-release: user-facing changelog for the pool right-sizing already shipped with PR #292's tegami entry; this completes that same change at the deployment layer.

🤖 Generated with Claude Code

PR #292 changed the application-prod.yml pool defaults to 8/8 but the
production compose layer still injected 12/2, overriding them at runtime.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kl3inIT, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 47f6929e-122f-45ea-8e86-029836a43f14

📥 Commits

Reviewing files that changed from the base of the PR and between 3f04c35 and 48a7e31.

📒 Files selected for processing (1)
  • infrastructure/deployment/compose.production.yaml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Tegami

This repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under .tegami/ before merging.

Create a changelog → · Changelog format

Release preview

Package Bump Version
orgmemory minor 0.2.00.3.0

This PR does not add changelog files. Pending changelogs from other branches are included in the preview above.

Run pnpm run tegami locally to create a changelog interactively.

Managed by Tegami.

@kl3inIT
kl3inIT merged commit a1c6b12 into main Aug 4, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant