page:recipes:recruiting tracker:laravel:private attachments

Host Recruiting Tracker with Laravel: Private Attachments

Summary

Deploy a recruiting tracker built with Laravel on Ample using the private document library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the recruiting tracker-specific behavior as your application code.

Resource Requirements

Infrastructure Requirements

  1. Compute
    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
    Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
  3. S3-compatible object storage
    Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework

Workload

Release Status

Support Status

Execution Status

Docs Only

Prerequisites

Tested Configuration

Workflow Steps

  1. Build and Start
    composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template.
  2. Implement the pattern on PostgreSQL
    The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).
  3. Wire Object Storage
    Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
  4. Deploy
    Run the synchronous deploy once and read the result.
  5. Verify
    Fetch the live URL and the pattern self-test route(s).

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Unknowns

Formats