游戏部署指南：here.now 零配置托管与 GitHub Pages 部署教程

game-deploy by opusgamelabs/game-creator

221 周安装量

94 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/opusgamelabs/game-creator --skill game-deploy

开发运维游戏部署策略

🇨🇳中文介绍

游戏部署

将您的浏览器游戏部署以供公开访问。here.now 是默认选项——零配置的即时静态托管。当您需要基于 git 的部署时，GitHub Pages 可作为替代方案。

here.now 部署（默认）

先决条件

已安装 here-now 技能 (npx skills add heredotnow/skill --skill here-now -g)
可选：用于永久托管的 $HERENOW_API_KEY 或 ~/.herenow/credentials

快速部署

npm run build
~/.agents/skills/here-now/scripts/publish.sh dist/

脚本会输出一个实时 URL，例如 https://<slug>.here.now/。

为何 here.now 是默认选项

零配置——无需路径，无需 git 仓库，无需 GitHub CLI

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

重要提示：在 24 小时内认领您的网站

没有 API 密钥时，发布是匿名的，并在 24 小时后过期。发布脚本会返回一个认领 URL——用户必须访问此 URL 并创建一个免费的 here.now 账户才能永久保留网站。认领令牌仅显示一次，无法恢复。 如果用户不认领，网站将消失。

每次匿名发布后，您都必须告知用户关于 24 小时窗口期和认领 URL 的信息。 这是强制要求。

功能	匿名	已认证
过期时间	24 小时（然后删除！）	永久
最大文件大小	250 MB	5 GB
速率限制	5次/小时/IP	60次/小时/账户

要为永久托管设置 API 密钥（完全跳过 24 小时窗口期）：

首先检查密钥是否已存在：test -f .env && grep -q '^HERENOW_API_KEY=.' .env && echo "found" 如果找到，使用 set -a; . .env; set +a 导出它并跳过提示。

向用户询问其电子邮件
发送一个魔法链接：curl -sS https://here.now/api/auth/login -H "content-type: application/json" -d '{"email": "user@example.com"}'
用户点击链接，从仪表板复制其 API 密钥
用户粘贴密钥，格式如：HERENOW_API_KEY=their-key-here（自动保存到 .env 并隐藏）
同时保存到凭证文件：mkdir -p ~/.herenow && grep '^HERENOW_API_KEY=' .env | cut -d= -f2- > ~/.herenow/credentials && chmod 600 ~/.herenow/credentials

npm run build
~/.agents/skills/here-now/scripts/publish.sh dist/ --slug <slug>

每次发布后，slug 会保存在 .herenow/state.json 中——脚本会自动加载它以进行更新。

添加到 package.json：

{
  "scripts": {
    "deploy": "npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/"
  }
}

对于更新现有 slug：

{
  "scripts": {
    "deploy": "npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/ --slug <slug>"
  }
}

GitHub Pages 部署（替代方案）

当您需要基于 git 的部署或已经设置了 GitHub 仓库时，请使用 GitHub Pages。

已安装 GitHub CLI (gh)
Git 仓库已初始化并推送到 GitHub

npm run build && npx gh-pages -d dist

确保 vite.config.js 具有正确的基础路径（如果部署到子目录）：

export default defineConfig({

  base: '/<repo-name>/',
  // ... 其余配置
});

3. 使用 GitHub CLI 部署：

gh repo create <game-name> --public --source=. --push
npm install -D gh-pages
npx gh-pages -d dist

4. 在仓库设置中启用 GitHub Pages（应自动检测 gh-pages 分支）。

您的游戏将在此地址上线：https://<username>.github.io/<repo-name>/

添加到 package.json：

{
  "scripts": {
    "deploy": "npm run build && npx gh-pages -d dist"
  }
}

部署后，在 Play.fun 上注册您的游戏以实现货币化。使用 /game-creator:playdotfun 技能获取集成详情。

部署后的 URL 在注册时将成为您的 gameUrl：

await client.games.register({
  name: '您的游戏名称',
  gameUrl: 'https://<slug>.here.now/',  // 或 GitHub Pages URL
  maxScorePerSession: 500,
  maxSessionsPerDay: 20,
  maxCumulativePointsPerDay: 5000
});

Vercel：npx vercel --prod（自动检测 Vite）
Netlify：连接仓库，将构建命令设置为 npm run build，发布目录设置为 dist
Railway：使用 Railway 技能进行部署
itch.io：将 dist/ 文件夹作为 HTML5 游戏上传

默认（here.now）

结果：构建 dist/ → 通过 here.now 发布 → 游戏在几秒钟内上线，地址为 https://<slug>.here.now/。为未来的一键部署添加 npm run deploy 脚本。

/game-deploy github-pages

结果：使用正确的基础路径构建 → 推送到 gh-pages 分支 → 游戏在 1-2 分钟内上线，地址为 https://<user>.github.io/<game>/。

here.now 429 速率限制

原因： 短时间内部署次数过多。here.now 对匿名部署有速率限制。解决方法： 等待几分钟后重试。对于频繁部署，请考虑改用 GitHub Pages 或 Vercel。

匿名 here.now 网站已过期

原因： 匿名 here.now 部署是临时的，在不活动一段时间后会过期。解决方法： 使用 npx here.now 重新部署。对于持久托管，请使用不会过期的 GitHub Pages（gh-pages 分支）或 Vercel。

部署后 GitHub Pages 出现 404

原因： Vite 的基础路径与 GitHub Pages 的 URL 结构（/<repo-name>/）不匹配。解决方法： 在 vite.config.js 中设置 base: '/<repo-name>/'。确保在仓库的 Pages 设置中选择 gh-pages 分支作为源。等待 1-2 分钟让 GitHub 的 CDN 传播。

部署后出现空白页面（资源路径）

原因： 资源路径使用了绝对 URL（/assets/...），在部署主机上无法正确解析。解决方法： 使用相对路径（./assets/...）或将 Vite 的 base 选项配置为与部署 URL 匹配。在部署前，本地运行 npm run build 并使用本地服务器测试 dist/ 文件夹。

gh-pages 推送被拒绝

原因： 远程 gh-pages 分支已分叉，或者强制推送被分支保护规则阻止。解决方法： 如果您拥有仓库且没有分支保护，请使用 git push origin gh-pages --force。如果受保护，请先删除远程 gh-pages 分支：git push origin --delete gh-pages，然后重新部署。

部署前检查清单

npm run build 成功且无错误
使用 npm run preview 测试生产构建
移除所有 console.log 调试语句
验证所有资源是否包含在构建中
检查移动端/响应式行为（如适用）
在 index.html 中设置适当的 <title> 和元标签

🇺🇸English

Game Deployment

Deploy your browser game for public access. here.now is the default — instant static hosting with zero configuration. GitHub Pages is available as an alternative when you need git-based deploys.

here.now Deployment (Default)

Prerequisites

The here-now skill installed (npx skills add heredotnow/skill --skill here-now -g)
Optional: $HERENOW_API_KEY or ~/.herenow/credentials for permanent hosting

Quick Deploy

npm run build
~/.agents/skills/here-now/scripts/publish.sh dist/

The script outputs a live URL like https://<slug>.here.now/.

Why here.now is the default

Zero config — no base path, no git repo, no GitHub CLI required
Instant — site is live immediately (no waiting for propagation)
No base path issues — content served from subdomain root (base: '/' or default)
Works everywhere — only needs curl, file, and jq

Vite base path

here.now serves from the subdomain root, so use the default base path:

export default defineConfig({
  base: '/',
  // ... rest of config
});

IMPORTANT: Claim your site within 24 hours

Without an API key, publishes are anonymous and expire in 24 hours. The publish script returns a claim URL — the user MUST visit this URL and create a free here.now account to keep the site permanently. The claim token is only shown once and cannot be recovered. If they don't claim it, the site disappears.

You MUST always tell the user about the 24-hour window and the claim URL after every anonymous publish. This is not optional.

Feature	Anonymous	Authenticated
Expiry	24 hours (then deleted!)	Permanent
Max file size	250 MB	5 GB
Rate limit	5/hour/IP	60/hour/account

To set up an API key for permanent hosting (skip the 24h window entirely):

First check if the key already exists: test -f .env && grep -q '^HERENOW_API_KEY=.' .env && echo "found" If found, export it with set -a; . .env; set +a and skip the prompt.

Otherwise:

Ask the user for their email
Send a magic link: curl -sS https://here.now/api/auth/login -H "content-type: application/json" -d '{"email": "user@example.com"}'
User clicks the link, copies their API key from the dashboard
User pastes the key like: HERENOW_API_KEY=their-key-here (saved to .env and redacted automatically)
Also save to credentials file: mkdir -p ~/.herenow && grep '^HERENOW_API_KEY=' .env | cut -d= -f2- > ~/.herenow/credentials && chmod 600 ~/.herenow/credentials

Updating a deploy

npm run build
~/.agents/skills/here-now/scripts/publish.sh dist/ --slug <slug>

The slug is saved in .herenow/state.json after each publish — the script auto-loads it for updates.

Deploy script

Add to package.json:

{
  "scripts": {
    "deploy": "npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/"
  }
}

For updates to an existing slug:

{
  "scripts": {
    "deploy": "npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/ --slug <slug>"
  }
}

GitHub Pages Deployment (Alternative)

Use GitHub Pages when you need git-based deployment or already have a GitHub repo set up.

Prerequisites

GitHub CLI installed (gh)
Git repository initialized and pushed to GitHub

Quick Deploy

npm run build && npx gh-pages -d dist

Full Setup

Build the game :

npm run build

Ensurevite.config.js has the correct base path if deploying to a subdirectory:

export default defineConfig({

  base: '/<repo-name>/',
  // ... rest of config
});

3. Deploy with GitHub CLI :

gh repo create <game-name> --public --source=. --push
npm install -D gh-pages
npx gh-pages -d dist

4. Enable GitHub Pages in repo settings (should auto-detect the gh-pages branch).

Your game is live at: https://<username>.github.io/<repo-name>/

Automated Deploys

Add to package.json:

{
  "scripts": {
    "deploy": "npm run build && npx gh-pages -d dist"
  }
}

Play.fun Registration

After deploying, register your game on Play.fun for monetization. Use the /game-creator:playdotfun skill for integration details.

The deployed URL becomes your gameUrl when registering:

await client.games.register({
  name: 'Your Game Name',
  gameUrl: 'https://<slug>.here.now/',  // or GitHub Pages URL
  maxScorePerSession: 500,
  maxSessionsPerDay: 20,
  maxCumulativePointsPerDay: 5000
});

Other Hosting Options

Vercel : npx vercel --prod (auto-detects Vite)
Netlify : Connect repo, set build command to npm run build, publish dir to dist
Railway : Use the Railway skill for deployment
itch.io : Upload the dist/ folder as an HTML5 game

Example Usage

Default (here.now)

/game-deploy

Result: Builds dist/ → publishes via here.now → game live at https://<slug>.here.now/ in seconds. Adds npm run deploy script for future one-command deploys.

GitHub Pages

/game-deploy github-pages

Result: Builds with correct base path → pushes to gh-pages branch → game live at https://<user>.github.io/<game>/ in 1-2 minutes.

Troubleshooting

here.now 429 rate limit

Cause: Too many deployments in a short period. here.now has rate limiting on anonymous deployments. Fix: Wait a few minutes and retry. For frequent deployments, consider using GitHub Pages or Vercel instead.

Anonymous here.now site expired

Cause: Anonymous here.now deployments are temporary and expire after a period of inactivity. Fix: Redeploy with npx here.now. For persistent hosting, use GitHub Pages (gh-pages branch) or Vercel, which don't expire.

GitHub Pages 404 after deployment

Cause: Vite's base path doesn't match the GitHub Pages URL structure (/<repo-name>/). Fix: Set base: '/<repo-name>/' in vite.config.js. Ensure the gh-pages branch is selected as the source in the repository's Pages settings. Wait 1-2 minutes for GitHub's CDN to propagate.

Blank page after deployment (asset paths)

Cause: Asset paths use absolute URLs (/assets/...) that don't resolve correctly on the deployment host. Fix: Use relative paths (./assets/...) or configure Vite's base option to match the deployment URL. Run npm run build locally and test the dist/ folder with a local server before deploying.

gh-pages push rejected

Cause: The remote gh-pages branch has diverged or the force push was blocked by branch protection rules. Fix: Use git push origin gh-pages --force if you own the repo and there's no branch protection. If protected, delete the remote gh-pages branch first: git push origin --delete gh-pages, then redeploy.

Pre-Deploy Checklist

npm run build succeeds with no errors
Test the production build with npm run preview
Remove any console.log debug statements
Verify all assets are included in the build
Check mobile/responsive behavior if applicable
Set appropriate <title> and meta tags in index.html

Weekly Installs

Repository

opusgamelabs/ga…-creator

GitHub Stars

First Seen

Feb 21, 2026

Security Audits

Gen Agent Trust HubWarn SocketWarn SnykPass

Installed on

claude-code72

opencode45

cursor43

github-copilot43

amp43

codex43

Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU

104,900 周安装

游戏部署指南：here.now 零配置托管与 GitHub Pages 部署教程

🇨🇳中文介绍

游戏部署

here.now 部署（默认）

先决条件

快速部署

为何 here.now 是默认选项

相关 Skills

Vite 基础路径

重要提示：在 24 小时内认领您的网站

更新部署

部署脚本

GitHub Pages 部署（替代方案）

先决条件

快速部署

完整设置

自动化部署

Play.fun 注册

其他托管选项

使用示例

默认（here.now）

GitHub Pages

故障排除

here.now 429 速率限制

匿名 here.now 网站已过期

部署后 GitHub Pages 出现 404

部署后出现空白页面（资源路径）

gh-pages 推送被拒绝

部署前检查清单

🇺🇸English

Game Deployment

here.now Deployment (Default)

Prerequisites

Quick Deploy

Why here.now is the default

Vite base path

IMPORTANT: Claim your site within 24 hours

Updating a deploy

Deploy script

GitHub Pages Deployment (Alternative)

Prerequisites

Quick Deploy

Full Setup

Automated Deploys

Play.fun Registration

Other Hosting Options

Example Usage

Default (here.now)

GitHub Pages

Troubleshooting

here.now 429 rate limit

Anonymous here.now site expired

GitHub Pages 404 after deployment

Blank page after deployment (asset paths)

gh-pages push rejected

Pre-Deploy Checklist

最新 Skills