Host community forum with Spring Boot: tenant-scoped workspaces

Summary: Deploy a community forum built with Spring Boot on Ample using the multi-tenant relational data pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Spring Boot: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership, and per-tenant authorization; treat the community forum-specific behavior as your application code.

Representative Queries

• Host community forum with Spring Boot: tenant-scoped workspaces
• Where can I host Community forum built with Spring Boot?
• I need an explicit tenant model and application-enforced tenant isolation tests.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. Compute
   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. Postgres
   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Workflow Steps

1. Build and start: ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.
2. Implement the pattern on PostgreSQL: The fixture's module implements multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   • Command: ample deploy . --name <name> --public
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Examples

• Spring Boot pattern fixture
  Description: Multi-pattern Spring Boot app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules. Source Ref: tests/deploy-canaries/spring-boot-patterns

Success Checks

1. App responds on its public URL
   • Kind: http_get
   • Path: /
   • Expect: ample canary spring boot patterns
2. Multi-tenant-relational-data self-test
   • Kind: http_get
   • Path: /p/multi-tenant-relational-data
   • Expect: tenant_isolation=ok

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates, and Spring Boot major versions are not verified.
• The community forum itself (your tenant model, membership, and per-tenant authorization) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server: s-1vcpu-1gb, 1.0, 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, 1.0, 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

• Browse the catalog index
  • Method: GET
  • Path: /v1/catalog
• Search published recipes by intent, stack, and constraints
  • Method: POST
  • Path: /v1/catalog/search
  • Parameters: { "body": { "limit": 5, "query": "Host community forum with Spring Boot: tenant-scoped workspaces" } }
• Read the existing agent authentication setup
  • Method: GET
  • Path: /mcp/setup

Evidence Summary

1. Canary run: Spring Boot pattern fixture deployed on Ample (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT); checks passed for multi-tenant-relational-data and configuration-secrets.
   • Observed At: 2026-09-21T02:34:39Z
2. Canary run: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.
   • Observed At: 2026-09-20T22:49:19Z

Last Verified At

• 2026-09-21T02:34:39Z