菜单
Guides Claude through deploying Gleam applications to production on Fly.io, Docker, or other platforms. Use when setting up deployment pipelines, configuring environments, or troubleshooting production issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gleam-deployment |
| description | Guides Claude through deploying Gleam applications to production on Fly.io, Docker, or other platforms. Use when setting up deployment pipelines, configuring environments, or troubleshooting production issues. |
This skill guides Claude Code through deploying Gleam applications to production.
Complete step-by-step guide: Gleam on Fly.io
Key points:
0.0.0.0 (use mist.bind("0.0.0.0"))flyctl deployGleam apps can deploy to any platform supporting:
Build optimized Erlang release:
gleam export erlang-shipment
This creates a standalone release in build/erlang-shipment/.
Build JavaScript bundle:
gleam build --target javascript
Output in build/dev/javascript/.
Example from Fly.io guide:
# Stage 1: Build
FROM ghcr.io/gleam-lang/gleam:v1.10.0-erlang-alpine AS builder
WORKDIR /app
COPY . .
RUN gleam export erlang-shipment
# Stage 2: Runtime
FROM erlang:27.1.1.0-alpine
WORKDIR /app
COPY --from=builder /app/build/erlang-shipment /app
RUN adduser -D webapp
USER webapp
ENTRYPOINT ["/app/entrypoint.sh"]
CMD ["run"]
See complete example: Fly.io Deployment Guide
Best practices:
Use Envoy for environment configuration:
import envoy
pub fn main() {
let assert Ok(port) = envoy.get("PORT")
|> result.then(int.parse)
let assert Ok(db_url) = envoy.get("DATABASE_URL")
start_server(port, db_url)
}
See: Envoy Documentation
For complex configuration, consider:
See: Wisp Security
Use connection pools for databases:
Patterns for database migrations:
See: Cigogne - Postgres migrations in Gleam
Production logging strategies:
BEAM/OTP monitoring:
:observer, :recon)Implement health check endpoints:
fn handle_request(req: Request) -> Response {
case wisp.path_segments(req) {
["health"] -> wisp.response(200)
|> wisp.set_body(wisp.Text("OK"))
// other routes...
}
}
gleam export erlang-shipment for optimized buildsname: Deploy
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Install Gleam
uses: erlef/setup-beam@v1
with:
gleam-version: "1.10.0"
- name: Run tests
run: gleam test
- name: Deploy to Fly.io
uses: superfly/flyctl-actions@master
with:
args: "deploy"
env:
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
Port binding: Ensure listening on 0.0.0.0, not localhost
Environment variables: Verify all required vars are set in platform
File permissions: Run as non-root user, check file ownership
Build failures: Check Dockerfile layer caching, dependencies
Strategies:
Remember: Gleam compiles to mature, battle-tested runtimes (BEAM, JavaScript). Focus on platform-specific deployment concerns.
Guides Claude through idiomatic Lustre frontend development. Use when building SPAs, UI components, or interactive applications. Based on lustre_ui patterns from the official Lustre team.
Guides Claude through Gleam backend web development with Wisp and Mist. Use for REST APIs, web services, and server-side rendering. For frontend/SPA development with Lustre, use the gleam-lustre-development skill instead.
Guides Claude through creating and publishing Gleam packages to Hex.pm. Use when developing libraries, writing documentation, or preparing packages for publication.
Guides Claude through testing Gleam applications with gleeunit. Use when writing unit tests, integration tests, or property-based tests. Always use let assert, NOT deprecated should module.
Guides Claude through integrating Gleam with Erlang and Elixir code using FFI, external functions, and BEAM libraries. Use when building for Erlang target, calling Erlang libraries, or integrating with existing BEAM systems.
Guides Claude through integrating Gleam with JavaScript code using FFI, external functions, and NPM packages. Use when building for JavaScript target, using browser APIs, or wrapping JS libraries.