el-foundation/hatch-surf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
df378d33ef
hatch-surf/node_modules/next/dist/docs/01-app/03-api-reference/07-adapters/11-use-cases.md
Riley Zhang df378d33ef
Some checks failed
CI / go (push) Waiting to run
Details
CI / docker (push) Waiting to run
Details
CI / lint-go (push) Waiting to run
Details
CI / lint-docs (push) Waiting to run
Details
CI / check-paperclip (push) Waiting to run
Details
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Details
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Details
Merge GitHub main into Gitea repo (allow unrelated histories) 
Resolved conflicts by taking GitHub versions for:
- .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml

Kept deploy.sh updated to:
- Pull from GitHub (primary source)
- Push to Gitea (push-mirror)
- Build from site/ directory (GitHub structure)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-25 05:20:46 +02:00

626 B
Raw Blame History

title description
Use Cases Common patterns and examples for deployment adapter implementations.

Common use cases for adapters include:

  • Deployment Platform Integration: Automatically configure build outputs for specific hosting platforms
  • Asset Processing: Transform or optimize build outputs
  • Monitoring Integration: Collect build metrics and route information
  • Custom Bundling: Package outputs in platform-specific formats
  • Build Validation: Ensure outputs meet specific requirements
  • Route Generation: Use processed route information to generate platform-specific routing configs