Skip to content

fix: isolate dynamic apps in per-app namespaces - #284

Merged
NathanFlurry merged 39 commits into
mainfrom
benches
Aug 31, 2026
Merged

NathanFlurry merged 39 commits into
mainfrom
benches

Conversation

@NathanFlurry

Copy link
Copy Markdown
Member

Summary

  • provision a dedicated Rivet Cloud namespace and scoped credentials per Dynamic App
  • keep deployment/build behavior while configuring app actor runners in the isolated namespace
  • add a real SQLite-backed actor fixture and update deployment documentation

Validation

  • local type checks and unit tests passed
  • local actor fixture executed SQLite mutations and reads

This PR intentionally contains the Dynamic Apps benchmark qualification stack already carried by the existing benches branch.

@railway-app

railway-app Bot commented Aug 31, 2026

Copy link
Copy Markdown

🚅 Environment dynamic-apps-pr-284 in rivet-frontend has no services deployed.


🚅 Deployed to the dynamic-apps-pr-284 environment in secure-exec

Service Status Web Updated (UTC)
secure-exec 🕒 Building (View Logs) Web Aug 31, 2026 at 7:21 am

@NathanFlurry
NathanFlurry merged commit 79a866c into main Aug 31, 2026
1 check was pending
@NathanFlurry
NathanFlurry deleted the benches branch August 31, 2026 07:21
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