page:recipes:approval workflow:laravel:private attachments
Host approval workflow with Laravel: private attachments
Deploy a approval workflow 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 approval workflow-specific behavior as your application code.
Queries
- Host approval workflow with Laravel: private attachments
- Where can I host Approval workflow built with Laravel?
- I need attachment metadata, access checks and a tested private object access path.
Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
Infrastructure Requirements
Compute
- Canonical Path: /discover/primitive/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.
Postgres
- Canonical Path: /discover/primitive/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.
S3-compatible object storage
- Canonical Path: /discover/primitive/s3-compatible-object-storage
- Status: verified
- Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
Framework
Laravel
Workflow Steps
- 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. The server must bind 0.0.0.0 on PORT. - 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command. - Wire object storage
Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. - 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.ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... - Verify
Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks. On failure readample logs --kind buildthen--kind runtime.ample logs --kind build
Limitations
- Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and Laravel major versions are not verified.
- The approval workflow itself (your identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations, and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits, and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs, and lifecycle rules are not.
Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Basis: size prices from pricing.toml (loaded by the API)...
Components
- App server
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: 5.0
- Managed PostgreSQL database
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: 5.0
Examples
Laravel pattern fixture
- Description: Multi-pattern Laravel app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
- Source Reference: tests/deploy-canaries/laravel-patterns
Success Checks
- App responds on its public URL
- Kind: http_get
- Path: /
- Expect: ample canary laravel patterns
- Private-document-library self-test
- Kind: http_get
- Path: /p/private-document-library
- Expect: private=ok (with ?role=owner; 401 without, 403 for viewer)
Evidence Summary
- Kind: canary_run
- Summary: Laravel pattern fixture deployed on Ample...
- Observed At: 2026-09-20T20:36:21Z
- Expires At: 2027-03-19T20:36:21Z
Formats
Next Actions
- Browse the catalog index
- Search published recipes by intent, stack and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse Approval workflow
- Browse Laravel
- Browse Private document library
- Browse Deploy web app