mirror of
https://github.com/BagelHole/DevOps-Security-Agent-Skills.git
synced 2026-08-22 12:49:53 +02:00
Add OpenClaw local and Mac mini setup skill
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: cloudflare-pages
|
||||
description: Deploy static sites and full-stack apps on Cloudflare Pages with previews, functions, and custom domains.
|
||||
license: MIT
|
||||
metadata:
|
||||
author: devops-skills
|
||||
version: "1.0"
|
||||
---
|
||||
|
||||
# Cloudflare Pages
|
||||
|
||||
Deploy frontend projects with preview builds and edge functions.
|
||||
|
||||
## Connect Project
|
||||
|
||||
1. Create a Pages project in Cloudflare dashboard.
|
||||
2. Link your GitHub repository.
|
||||
3. Set build command and output directory.
|
||||
4. Configure environment variables per environment.
|
||||
|
||||
## Wrangler-Based Deploy
|
||||
|
||||
```bash
|
||||
npm install -D wrangler
|
||||
npx wrangler pages project create my-site
|
||||
npx wrangler pages deploy dist --project-name=my-site
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Require previews for pull requests.
|
||||
- Separate production and preview secrets.
|
||||
- Enable Web Analytics for performance visibility.
|
||||
- Add Cloudflare WAF rules for abuse protection.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- [cloudflare-workers](../cloudflare-workers/) - Edge backend logic
|
||||
- [vercel-deployments](../../platforms/vercel-deployments/) - Alternative frontend hosting
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
name: cloudflare-r2
|
||||
description: Manage Cloudflare R2 buckets, lifecycle, and signed URLs. Use for low-egress object storage and media delivery.
|
||||
license: MIT
|
||||
metadata:
|
||||
author: devops-skills
|
||||
version: "1.0"
|
||||
---
|
||||
|
||||
# Cloudflare R2
|
||||
|
||||
Use S3-compatible object storage without egress fees.
|
||||
|
||||
## Setup
|
||||
|
||||
```bash
|
||||
# Create bucket
|
||||
npx wrangler r2 bucket create app-assets
|
||||
|
||||
# List buckets
|
||||
npx wrangler r2 bucket list
|
||||
|
||||
# Upload object
|
||||
npx wrangler r2 object put app-assets/logo.png --file ./logo.png
|
||||
```
|
||||
|
||||
## S3-Compatible Access
|
||||
|
||||
- Generate R2 API tokens with least privilege.
|
||||
- Use endpoint format: `https://<accountid>.r2.cloudflarestorage.com`.
|
||||
- Configure lifecycle rules for archive/delete.
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Use short-lived signed URLs for private content.
|
||||
- Store user uploads in tenant-specific prefixes.
|
||||
- Enable object versioning for recovery-critical buckets.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- [cloudflare-workers](../cloudflare-workers/) - Signed URL generation
|
||||
- [object-storage](../../storage/object-storage/) - Storage patterns
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: cloudflare-workers
|
||||
description: Build and deploy edge functions with Cloudflare Workers and Wrangler. Use for APIs, cron jobs, and edge middleware.
|
||||
license: MIT
|
||||
metadata:
|
||||
author: devops-skills
|
||||
version: "1.0"
|
||||
---
|
||||
|
||||
# Cloudflare Workers
|
||||
|
||||
Deploy JavaScript/TypeScript functions globally at the edge.
|
||||
|
||||
## Quick Start
|
||||
|
||||
```bash
|
||||
npm create cloudflare@latest my-worker
|
||||
cd my-worker
|
||||
npx wrangler login
|
||||
npx wrangler deploy
|
||||
```
|
||||
|
||||
## Common Commands
|
||||
|
||||
```bash
|
||||
# Local dev
|
||||
npx wrangler dev
|
||||
|
||||
# Set secret
|
||||
npx wrangler secret put API_TOKEN
|
||||
|
||||
# Tail logs
|
||||
npx wrangler tail
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Keep workers stateless and fast.
|
||||
- Use KV, D1, or R2 for persistence.
|
||||
- Add rate limits for public APIs.
|
||||
- Version Wrangler config in git.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- [cloudflare-pages](../cloudflare-pages/) - Frontend deployments
|
||||
- [cloudflare-r2](../cloudflare-r2/) - Object storage at the edge
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: cloudflare-zero-trust
|
||||
description: Protect internal apps with Cloudflare Access, device posture, and Zero Trust policies.
|
||||
license: MIT
|
||||
metadata:
|
||||
author: devops-skills
|
||||
version: "1.0"
|
||||
---
|
||||
|
||||
# Cloudflare Zero Trust
|
||||
|
||||
Secure access to internal services without exposing public VPN endpoints.
|
||||
|
||||
## Core Workflow
|
||||
|
||||
1. Register application in Cloudflare Access.
|
||||
2. Integrate identity provider (Google Workspace, Okta, Entra ID).
|
||||
3. Define access policies by group, email domain, and device posture.
|
||||
4. Add logging and alerts for blocked requests.
|
||||
|
||||
## Tunnel Setup
|
||||
|
||||
```bash
|
||||
cloudflared tunnel login
|
||||
cloudflared tunnel create internal-app
|
||||
cloudflared tunnel route dns internal-app app.example.com
|
||||
cloudflared tunnel run internal-app
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Enforce MFA and managed-device posture checks.
|
||||
- Use service tokens for CI/CD automation.
|
||||
- Review app policies quarterly.
|
||||
|
||||
## Related Skills
|
||||
|
||||
- [zero-trust](../../../security/network/zero-trust/) - Zero trust architecture fundamentals
|
||||
- [dns-management](../../networking/dns-management/) - DNS routing concepts
|
||||
Reference in New Issue
Block a user