# Host help desk with Laravel: relational workspace data

Deploy a help desk built with Laravel on Ample using the relational records 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 Laravel: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the help desk-specific behavior as your application code.

## Representative Queries
- Host help desk with Laravel: relational workspace data
- Where can I host Help desk built with Laravel?
- I need a workspace-specific schema, state transitions and access rules.

## Resource Requirements
- primitive:compute
- primitive: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.

## 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)
- An Ample account token with servers:write, databases:read

## 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. The server must bind 0.0.0.0 on PORT.
   
2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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.  
   ```
   ample deploy . --name  --public
   ```
   
4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   ```
   ample logs  --kind build
   ```

## Tested Configuration
- **Template:** php-8.5  
- **Runtime:** php  
- **Size:** s-1vcpu-1gb  
- **Install:** composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader  
- **Start:** frankenphp php-server --listen :$PORT --root public

## Output Schema
### Input Schema
- **Required:**  
  - name  
  - path  
- **Properties:**  
  - env
    - *Description:* Encrypted environment variables (bucket credentials, secrets)
    - *Type:* array
  - name  
    - *Description:* App name
  - path
    - *Description:* Project directory or ample.toml service  
  - release_command  
    - *Description:* Migration command run before activation

## Success Checks
1. **App responds on its public URL**  
   - *Kind:* http_get  
   - *Path:* /  
   - *Expect:* ample canary laravel patterns  
 
2. **Relational-records self-test**  
   - *Kind:* http_get  
   - *Path:* /p/relational-records  
   - *Expect:* records=ok transitions=true isolation=true

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

## 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 help desk itself (your record schema, states, and access rules) is application code and was not separately tested; the pattern checks are what was verified.

## Evidence Summary
- *Kind:* canary_run  
  - *Summary:* Laravel pattern fixture deployed on Ample (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). Checks passed for relational-records and configuration-secrets. 
  - *Observed At:* 2026-09-20T20:36:21Z  
- *Last Verified At:* 2026-09-20T20:36:21Z

## 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 Help desk**  
- **Browse Laravel**  
- **Browse Relational records**  
- **Browse Deploy web app**