page:recipes:inventory manager:laravel:report exports
Host Inventory Manager with Laravel: Downloadable Reports
Deploy an inventory manager built with Laravel on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the inventory manager-specific behavior as your application code.
Representative Queries
- Host inventory manager with Laravel: downloadable reports
- Where can I host Inventory manager built with Laravel?
- I need an export query, generated artifact retention, and authorized download flow.
Resource Requirements
primitive:computeprimitive:postgresprimitive:s3-compatible-object-storage
Infrastructure Requirements
- Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- 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.
- S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
Prerequisites
- A Laravel project that builds and starts with the documented commands (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)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variables - An Ample account token with servers:write, databases:read, buckets:read
Workflow Steps
- Build and Start: Run
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: 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.
- Verify: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read
ample logs --kind buildthen--kind runtime.
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 inventory manager itself (your export formats, retention policy, and entitlement model) 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)
Evidence Summary
- Kind: Canary Run
- Summary: Laravel pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets. An export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller.
- Observed At: 2026-09-20T20:36:21Z
- Expires At: 2027-03-19T20:36:21Z
Example
- Title: Laravel pattern fixture
- Description: Multi-pattern Laravel app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
- Source Ref: tests/deploy-canaries/laravel-patterns