[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73750":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":41,"readmeContent":42,"aiSummary":43,"trendingCount":16,"starSnapshotCount":16,"syncStatus":44,"lastSyncTime":45,"discoverSource":46},73750,"pinme","glitternetwork\u002Fpinme","glitternetwork","Deploy Your Frontend in a Single Command. Claude Code Skills supported.","https:\u002F\u002Fpinme.eth.limo",null,"TypeScript",3635,266,14,4,0,24,38,438,72,29.28,"MIT License",false,"main",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"ai-tools","claude-code-skill","claude-skills","deployment","deployment-tools","frontend","frontend-deployment","hosting","serverless","skills","static-site","static-site-deploy","static-site-hosting","web-hosting","zero-configuration","2026-06-12 02:03:17","\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fpinme.eth.limo\u002F\">\n    \u003Cimg src=\"https:\u002F\u002F2egc5b44.pinit.eth.limo\u002F\" height=\"92\" alt=\"PinMe logo\">\n    \u003Ch3 align=\"center\">PinMe\u003C\u002Fh3>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  Create and deploy your web in one command.\n\u003C\u002Fp>\n\n# PinMe\n\n[PinMe](https:\u002F\u002Fpinme.eth.limo\u002F) is a zero-config deployment CLI focused on one-command creation and deployment for full-stack projects.\n\nIt lets you quickly set up and launch a complete project with an integrated frontend, Worker backend, and database, without tedious configuration. PinMe is built to make full-stack delivery much simpler and significantly improve development efficiency.\n\nWebsite: [https:\u002F\u002Fpinme.eth.limo\u002F](https:\u002F\u002Fpinme.eth.limo\u002F)\n\n> **PinMe Skill**\n>\n> Install the PinMe skill before using PinMe in agent workflows:\n>\n> ```bash\n> npx skills add glitternetwork\u002Fpinme\n> ```\n\n## Table of Contents\n\n- [Quick Start](#quick-start)\n- [For AI Agents](#for-ai-agents)\n- [Installation](#installation)\n- [PinMe Project Workflow](#pinme-project-workflow)\n- [Authentication and Account Commands](#authentication-and-account-commands)\n- [Static Uploads and IPFS Utilities](#static-uploads-and-ipfs-utilities)\n- [Command Reference](#command-reference)\n- [Limits and Operational Notes](#limits-and-operational-notes)\n- [Examples](#examples)\n- [Support](#support)\n\n## Quick Start\n\n### Prerequisites\n\n- Node.js `>= 16.13.0`\n\n### Create a new Worker project\n\n```bash\nnpm install -g pinme\npinme login\npinme create my-app\ncd my-app\npinme save\n```\n\nWhat this workflow gives you:\n\n- a generated PinMe project from the official template\n- platform-side Worker and database provisioning\n- local project config in `pinme.toml`\n- frontend and Worker deployment from one CLI\n\n### Update only the part you changed\n\n```bash\npinme update-worker\npinme update-db\npinme update-web\n```\n\n### Upload a static build when you do not need the project workflow\n\n```bash\npinme login\npinme upload dist\n```\n\nCommon build directories are `dist`, `build`, `out`, and `public`.\n\n## For AI Agents\n\nPrefer the PinMe project workflow when the user wants a frontend plus backend plus database, or when the repo already contains `pinme.toml`.\n\n### Project-mode protocol\n\nUse this flow when the user wants a Worker app, database migrations, or ongoing project updates.\n\n1. Check Node.js:\n\n```bash\nnode --version\n```\n\n2. Ensure the CLI is available:\n\n```bash\nnpm install -g pinme\n```\n\n3. Authenticate:\n\n```bash\npinme login\n```\n\n4. Choose the right project command:\n\n- create a new project: `pinme create \u003Cname>`\n- deploy everything from a PinMe project root: `pinme save`\n- update Worker only: `pinme update-worker`\n- update SQL migrations only: `pinme update-db`\n- update frontend only: `pinme update-web`\n\n5. If the repo contains `pinme.toml`, run project commands from that directory.\n\n6. Return the final project URL printed by the CLI for frontend deploys. For Worker-only or DB-only updates, return the relevant success result instead of fabricating a URL.\n\n### Static-upload fallback\n\nUse this only when the task is just \"publish the built frontend\" and there is no PinMe project workflow involved.\n\n1. Authenticate:\n\n```bash\npinme login\n```\n\nOr for automation:\n\n```bash\npinme set-appkey \u003CAppKey>\n```\n\n2. Find the built output directory in this order:\n\n- `dist\u002F`\n- `build\u002F`\n- `out\u002F`\n- `public\u002F`\n\n3. Verify the directory exists and contains built assets such as `index.html`.\n\n4. Upload it:\n\n```bash\npinme upload \u003Cfolder>\n```\n\n### Guardrails\n\n- Do not upload source folders such as `src\u002F`.\n- Do not upload `node_modules`, `.git`, or `.env`.\n- Do not claim unsupported backend hosting outside the PinMe project template flow.\n- For project commands, do not run `update-*` commands outside a PinMe project root with `pinme.toml`.\n\n## Installation\n\nInstall from npm:\n\n```bash\nnpm install -g pinme\n```\n\nVerify installation:\n\n```bash\npinme --version\n```\n\n## PinMe Project Workflow\n\n### What `create` sets up\n\n`pinme create \u003Cname>` does more than scaffold files. The command:\n\n- requires an authenticated session\n- creates the platform project resources first\n- downloads the official Worker project template\n- writes project metadata into `pinme.toml`\n- writes backend metadata and frontend config files\n- installs workspace dependencies\n- builds the Worker\n- uploads Worker code and SQL files\n- builds the frontend and attempts an initial frontend upload\n\nAfter creation, the CLI prints the project management URL and suggests `pinme save` for the next deploy.\n\n### Create a project\n\n```bash\npinme login\npinme create my-app\n```\n\nIf the target directory already exists, the CLI asks before overwriting it unless `--force` is used.\n\n### Deploy the whole project\n\nRun this from the project root that contains `pinme.toml`:\n\n```bash\npinme save\npinme save --domain my-site\npinme save --domain example.com\n```\n\n`save` performs the full deploy path:\n\n- installs project dependencies\n- builds the Worker with `npm run build:worker`\n- uploads Worker code and SQL files from `db\u002F`\n- builds the frontend with `npm run build:frontend`\n- uploads `frontend\u002Fdist`\n- optionally binds a domain after the frontend deploy\n\n### Update only one layer\n\nUse targeted commands when only one part changed:\n\n```bash\npinme update-worker\npinme update-db\npinme update-web\n```\n\nWhat each command expects:\n\n- `update-worker`: builds and uploads Worker code from the current PinMe project\n- `update-db`: uploads `.sql` files from `db\u002F`\n- `update-web`: builds and uploads `frontend\u002Fdist`\n\n### Delete a project\n\n```bash\npinme delete\npinme delete my-app\npinme delete my-app --force\n```\n\nThis deletes the platform-side Worker, domain binding, and D1 database. Local files remain unchanged.\n\n## Authentication and Account Commands\n\n### Login and AppKey\n\n```bash\npinme login\npinme login --env test\n\npinme set-appkey\npinme set-appkey \u003CAppKey>\n\npinme show-appkey\npinme appkey\n\npinme logout\n```\n\nNotes:\n\n- `pinme login` is the recommended path for project commands.\n- `set-appkey` is the alternative authentication method for CLI and automation usage.\n\n### Domains, wallet, and history\n\n```bash\npinme my-domains\npinme domain\n\npinme wallet\npinme wallet-balance\npinme balance\n\npinme list\npinme ls\npinme list -l 5\npinme list -c\n```\n\n## Static Uploads and IPFS Utilities\n\nThese commands are useful when you already have artifacts and do not need the full Worker project flow.\n\n### Upload a directory or file\n\n```bash\npinme upload\npinme upload .\u002Fdist\npinme upload .\u002Fdist --domain my-site\npinme upload .\u002Fdist --domain example.com\npinme upload .\u002Fdist --domain my-site --dns\n```\n\nDomain handling:\n\n- domains containing a dot are treated as DNS domains\n- domains without a dot are treated as PinMe subdomains\n- `--dns` forces DNS mode\n\n### Bind while uploading\n\n```bash\npinme bind .\u002Fdist --domain my-site\npinme bind .\u002Fdist --domain example.com\n```\n\n`bind` requires wallet balance.\n\n### Import or export CAR files\n\n```bash\npinme import\npinme import .\u002Fsite.car\npinme import .\u002Fsite.car --domain my-site\n\npinme export \u003Ccid>\npinme export \u003Ccid> --output .\u002Fexports\n```\n\n### Remove uploaded content\n\n```bash\npinme rm\npinme rm \u003Cvalue>\n```\n\n## Command Reference\n\n| Command                                                   | What it does                                                 |\n| --------------------------------------------------------- | ------------------------------------------------------------ |\n| `pinme create [name]`                                     | Create a new PinMe Worker project from the official template |\n| `pinme save [--domain \u003Cname>]`                            | Deploy the current PinMe project: Worker, SQL, and frontend  |\n| `pinme update-worker`                                     | Build and upload Worker code only                            |\n| `pinme update-db`                                         | Upload SQL migrations from `db\u002F` only                        |\n| `pinme update-web`                                        | Build and upload the frontend only                           |\n| `pinme delete [name] [--force]`                           | Delete a platform project                                    |\n| `pinme upload [path]`                                     | Upload a file or directory to IPFS                           |\n| `pinme bind [path] --domain \u003Cname>`                       | Upload and bind a domain                                     |\n| `pinme import [path]`                                     | Import a CAR file                                            |\n| `pinme export \u003Ccid> [--output \u003Cdir>]`                     | Export IPFS content as a CAR file                            |\n| `pinme rm [value]`                                        | Remove uploaded content                                      |\n| `pinme login [--env test\\|prod]`                          | Login via browser                                            |\n| `pinme set-appkey [AppKey]`                               | Set authentication with an AppKey                            |\n| `pinme show-appkey` \u002F `pinme appkey`                      | Show masked AppKey info                                      |\n| `pinme my-domains` \u002F `pinme domain`                       | List domains owned by the current account                    |\n| `pinme wallet` \u002F `pinme wallet-balance` \u002F `pinme balance` | Show current wallet balance                                  |\n| `pinme list` \u002F `pinme ls`                                 | Show upload history                                          |\n| `pinme help`                                              | Show CLI help                                                |\n\n## Limits and Operational Notes\n\n- Default single-file upload limit: `100MB`\n- Default directory upload limit: `500MB`\n- These upload defaults come from the CLI and can be overridden with environment variables\n- `update-db` enforces a total SQL payload limit of `10MB` per run\n- `upload`, `import`, and project commands require authentication\n- domain binding requires wallet balance\n- `save`, `update-worker`, `update-db`, and `update-web` expect to run from a PinMe project root with `pinme.toml`\n\n## Examples\n\nThis repo includes example projects and docs:\n\n- [example\u002Fdocs](.\u002Fexample\u002Fdocs)\n- [example\u002Fpinme-blog](.\u002Fexample\u002Fpinme-blog)\n- [example\u002Fsupabase](.\u002Fexample\u002Fsupabase)\n\n## Support\n\n- Website: [https:\u002F\u002Fpinme.eth.limo\u002F](https:\u002F\u002Fpinme.eth.limo\u002F)\n- GitHub: [https:\u002F\u002Fgithub.com\u002Fglitternetwork\u002Fpinme](https:\u002F\u002Fgithub.com\u002Fglitternetwork\u002Fpinme)\n","PinMe 是一个专注于通过单个命令创建和部署全栈项目的零配置CLI工具。它支持前端、Worker后端以及数据库的一体化快速搭建与发布，无需繁琐的配置过程，极大地简化了开发流程并提高了效率。该工具使用TypeScript编写，具备静态站点部署、无服务器托管等功能，并且集成了Claude代码技能以增强自动化能力。适用于需要快速启动Web应用或静态网站的场景，特别是在希望减少初期设置时间、加速迭代周期的开发者团队中表现尤为出色。",2,"2026-06-11 03:47:12","high_star"]