메뉴
Deploy the Hyperindex frontend and backend to Railway. Use this skill when the user asks to deploy, redeploy, or update the production services on Railway.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/GainForest/hyperindex --skill deploy-railway명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Query the Hypercerts Hyperindex GraphQL indexer for ATProto hypercert records. Use when consumers need GraphQL queries, filters, pagination, sorting, or workflows for org.hypercerts.* and app.certified.* records on api.indexer.hypercerts.dev or dev.api.indexer.hypercerts.dev.
Polish Hyperindex's generated Changie release notes on the release/changelog branch into clear, human-friendly release notes while preserving factual scope and keeping the version file and CHANGELOG.md synchronized. Use whenever the user asks to review, rewrite, humanize, curate, polish, or finalize generated release notes or a changelog release PR. Do not use this skill to create individual unreleased fragments, choose a version bump, tag, publish, or deploy a release.
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | deploy-railway |
| description | Deploy the Hyperindex frontend and backend to Railway. Use this skill when the user asks to deploy, redeploy, or update the production services on Railway. |
Hyperindex is a monorepo with two Railway services:
| Service | Source | Dockerfile | Railway Name |
|---|---|---|---|
| Backend (Go) | repo root / | Dockerfile | backend |
| Frontend (Next.js) | client/ | client/Dockerfile | frontend |
| Service | Domain |
|---|---|
| Backend | https://api.hi.gainforest.app |
| Frontend | https://hi.gainforest.app |
Legacy domains (still active): backend-production-95a22.up.railway.app, frontend-production-dcce.up.railway.app
railway whoami)railway status should show project hyperindextap-feature)The backend deploys from the repo root using the root Dockerfile:
railway up -s backend -d
This uploads the entire repo, builds the Go binary in Docker, and deploys it. Takes ~3-5 minutes.
curl -s https://api.hi.gainforest.app/
# Should return: {"name":"Hyperindex","version":"0.1.0-dev",...}
CRITICAL: The frontend MUST use --path-as-root to avoid Railway picking up the root Go Dockerfile:
railway up --path-as-root client/ -s frontend -d
This makes client/ the archive root so Railway only sees client/Dockerfile (the Next.js build). Takes ~3-5 minutes.
--path-as-root?Without it, railway up uploads the entire monorepo and Railway finds the root Dockerfile (Go backend) instead of client/Dockerfile (Next.js frontend). This causes the frontend service to run the Go binary instead of the Next.js app.
curl -s -o /dev/null -w "%{http_code}" https://hi.gainforest.app/
# Should return: 200
# Verify it's actually Next.js (not the Go server):
curl -s https://hi.gainforest.app/ | grep -o '<title>[^<]*</title>'
# Should return: <title>Hyperindex</title>
# Backend (from repo root)
railway up -s backend -d
# Frontend (with path-as-root)
railway up --path-as-root client/ -s frontend -d
backend service)| Variable | Value |
|---|---|
HOST | 0.0.0.0 |
PORT | 8080 |
DATABASE_URL | sqlite:/app/data/hyperindex.db |
EXTERNAL_BASE_URL | https://api.hi.gainforest.app |
ADMIN_API_KEY | (must match frontend HYPERINDEX_ADMIN_API_KEY for proxied admin requests) |
ADMIN_DIDS | did:plc:qc42fmqqlsmdq7jiypiiigww (daviddao.org) |
OAUTH_LOOPBACK_MODE | true |
SECRET_KEY_BASE | (set on Railway, do not change) |
frontend service)| Variable | Value |
|---|---|
PORT | 3000 |
NEXT_PUBLIC_CLIENT_URL | https://hi.gainforest.app |
NEXT_PUBLIC_HYPERINDEX_URL | https://api.hi.gainforest.app |
HYPERINDEX_URL | https://api.hi.gainforest.app |
HYPERINDEX_ADMIN_API_KEY | (must match backend ADMIN_API_KEY; used by the Next.js admin proxy only) |
COOKIE_SECRET | (set on Railway, do not change) |
ATPROTO_JWK_PRIVATE | (ES256 JWK, set on Railway, do not change) |
Note: NEXT_PUBLIC_HYPERINDEX_URL is a build-time variable (inlined by Next.js during npm run build). HYPERINDEX_ADMIN_API_KEY is server-side only and must be set as a runtime variable on the frontend service.
You forgot --path-as-root client/. Redeploy with:
railway up --path-as-root client/ -s frontend -d
SSL certificate is still provisioning. Wait 5-15 minutes after adding DNS records.
GraphiQL is served directly by the backend. The frontend has a /graphiql server-side redirect route that redirects to https://api.hi.gainforest.app/graphiql.
Check that ATPROTO_JWK_PRIVATE and NEXT_PUBLIC_CLIENT_URL are set on the frontend service. Generate a new JWK with:
node scripts/generate-jwk.js # (in hyperscan repo, or client/scripts/ if copied)
Ensure the frontend HYPERINDEX_ADMIN_API_KEY matches the backend ADMIN_API_KEY. Without matching keys, the backend ignores the X-User-DID header from the Next.js proxy.
# Set a variable on a service
railway variables set 'KEY=value' -s backend
railway variables set 'KEY=value' -s frontend
# View all variables for a service
railway variables -s backend
railway variables -s frontend
After changing env vars, redeploy the affected service.