「vps」の検索結果

ConoHa VPS MCPサーバーの操作ガイド。サーバー作成・削除・起動・停止・リサイズ、ボリューム管理、セキュリティグループ設定、オブジェクトストレージ操作など、ConoHa VPS APIをMCPツールで操作する際に参照する。「ConoHa」「VPS」「サーバー作成」「サーバー削除」「ボリューム」「セキュリティグループ」「オブジェクトストレージ」「conoha_get」「conoha_post」「conoha_delete」「フレーバー」「イメージ」「SSHキーペア」「スタートアップスクリプト」などのキーワードで発動する。

VPS 安全加固自动化 Skill。通过 SSH 登录 VPS 并执行完整的安全策略配置。 触发场景： - "加固VPS安全"、"VPS安全配置"、"新VPS初始化" - "配置SSH安全"、"修改SSH端口"、"禁用root密码登录" - "VPS安全加固"、"服务器安全设置"、"hardening" 功能（7招安全加固）： 1. 创建 sudo 用户，禁用 root 密码登录 2. 修改 SSH 端口（支持 Ubuntu 不同版本） 3. Fail2ban 自动安装配置 4. SSH 密钥登录支持 5. SSH 登录通知（可选） 6. UFW 防火墙配置 7. Docker 安全提醒 Author: github.com/wlzh Version: 1.0.0

日本語の概要は準備中です。原文の説明を表示しています。

一键部署 VPS + VPN + Clash 代理环境。适合已购买 VMiss 或 DMIT 服务器、想通过干净 IP 访问 Claude/ChatGPT 等 AI 工具的用户。 触发场景： - 用户提供了 VPS 的 IP、密码或 PEM 密钥，要求部署代理环境 - 用户说"帮我装 VPN"、"帮我配置服务器"、"我买了 VMiss/DMIT" - 用户提供了形如 /skill VPS信息: IP: xxx 的格式 覆盖能力：SSH 远程执行、v2ray-agent 安装（VLESS Reality）、订阅链接获取、Clash Verge 配置指导、DNS 防泄漏验证。 只要用户提供了 VPS 凭据并表达想配代理，ALWAYS invoke this skill。

日本語の概要は準備中です。原文の説明を表示しています。

ConoHa VPS MCPサーバーの動作確認テストを自動実行するスキル。 「ConoHa テスト」「MCP動作確認」「動作検証」「conoha-test」「MCPテスト」 「VPSテスト」「検証項目」などのキーワードで発動する。

Audit and harden VPS security — fail2ban, SSH hardening, firewall setup

日本語の概要は準備中です。原文の説明を表示しています。

Systematic VPS cleanup — analyze files, categorize by importance, safely delete temporary/old data to free disk space

日本語の概要は準備中です。原文の説明を表示しています。

Dokploy is an open-source, self-hosted platform (an alternative to Heroku, Vercel and Netlify) that deploys applications, Docker Compose stacks and databases on your own server with Docker Swarm and Traefik, a web dashboard, automatic Let's Encrypt certificates and an HTTP API. Use when a user asks to "install Dokploy on a VPS", "deploy an app with Dokploy", "deploy a docker-compose project to Dokploy", "add a domain with HTTPS", "trigger a Dokploy deployment from CI", "create a Postgres database in Dokploy" or "set up zero-downtime deploys".

日本語の概要は準備中です。原文の説明を表示しています。

独立开发者与微型 SaaS — 单人或极小团队 (≤3 人) 构建可持续订阅收入的软件产品商业, 有别于自由职业/咨询、企业级 SaaS 和开源维护: (a) 产品发现与验证 (自己的痒 vs 市场优先 Nugent/Walling; 着陆页冒烟测试; 先接 Stripe 再写代码; JTBD 访谈适配独立开发者场景; Reddit/HN/X/社区痛点挖掘; Mom Test 验证框架; 公开构建作为验证机制); (b) 独立开发者技术架构 (无聊技术论 McKinley; 单体优先; serverless vs VPS 在 ≤$100/月预算下的取舍; Rails/Django/Laravel/Next.js 等框架的出货速度选型; 托管服务优先于自建; Supabase/PlanetScale/Neon 数据库即服务; Clerk/Auth0 认证即服务; Stripe/Paddle/LemonSqueezy 支付; Vercel/Fly.io/Railway 部署; AI 辅助编码 Cursor/Copilot 作为力量倍增器); (c) 无营销团队的分发与增长 (SEO 作为微型 SaaS 护城河; Product Hunt 发布; AppSumo 终身授权利弊; 冷邮件; Twitter/X 公开构建; IndieHackers 社区分发; 集成市场 Shopify/WordPress/Zapier/Slack 应用目录; 联盟计划; 一人内容营销); (d) 定价与变现 (SaaS 定价心理学; freemium vs 免费试用 vs 纯付费; 按席位 vs 按用量 vs 固定费率; 年付折扣; 老用户保价; 微型 SaaS 流失率控制; MRR/ARR/LTV/CAC 在微型规模的含义; $10K MRR 里程碑心理学); (e) 独立创始人心智模型与生活设计 (default alive vs default dead Graham; 拉面盈利 Levels; 生活方式生意 vs 增长生意的光谱; 独立开发者倦怠预防; 时间管理与上下文切换成本; 地理套利与远程优先; 一次构建反复销售的资产思维; 社区作为支持网络 IndieHackers/WIP/MicroConf); (f) 法务与运营基础 (公司注册地选择 LLC/Ltd/GmbH 税效; Stripe Atlas vs Firstbase vs 本地律师; 服务条款与隐私政策; GDPR/CCPA 低成本合规; 知识产权基础; 首次雇人的承包商 vs 员工选择; 独立开发者会计 SaaS — Xero/QuickBooks; 多辖区税务义务)。中国独立开发者生态: 出海作为主导策略 (从中国构建面向全球市场的产品以避开国内竞争/监管); 即刻/V2EX/少数派作为社区枢纽; 微信小程序作为替代分发; 小报童/爱发电作为中文市场变现; 人民币定价心理学; 支付宝/微信支付集成; ICP 备案要求; 中国区 App Store 审核差异; 独立开发者周刊。诚实处理: 生存偏差 (每一个 Pieter Levels 背后是数千个从未达到 $1K MRR 的人), AI 对微型 SaaS 生态位的颠覆 (wrapper 产品脆弱), 独自构建的孤独与心理健康成本, 公开构建的表演性质 vs 真正透明, AppSumo 终身授权上瘾毁坏单位经济, 样板代码销售的伦理边界。不含: 企业级 SaaS (不同 GTM/销售/融资模型), 不含: 自由职业/咨询 (用时间换钱非建资产), 不含: 开源维护 (不同可持续性模型), 不含: 风投支持的创业 (不同增长期望), 不含: 无代码/低代码平台构建 (相邻但不同受众), 不含: 内容创作作为主业。 (Independent Developer and Micro-SaaS — the craft of single-person or tiny-team (≤3 people) software product businesses that generate sustainable recurring revenue without venture capital, distinct from freelancing/consulting, enterprise SaaS, and open-source maintainership: (a) product discovery and validation (scratching your own itch vs market-first Nugent/Walling; landing page smoke tests; Stripe checkout before code; Jobs-to-Be-Done interview adapted to solo context; Reddit/HN/X/community pain-point mining; idea validation frameworks Fitzpatrick Mom Test; build-in-public as validation mechanism); (b) technical architecture for solo operators (boring technology thesis Mckinley; monolith-first; serverless vs VPS tradeoffs for ≤$100/mo infra; framework selection for shipping speed — Rails/Django/Laravel/Next.js/Remix/SvelteKit; managed services over self-hosted whenever possible; database-as-a-service Supabase/PlanetScale/Neon/Turso; auth-as-a-service Clerk/Auth0/Supabase Auth; payment integration Stripe/Paddle/LemonSqueezy; deployment Vercel/Fly.io/Railway/Render; monorepo vs polyrepo for solo; AI-assisted coding Cursor/Copilot as force multiplier); (c) distribution and growth without a marketing team (SEO as moat for micro-SaaS Ahrefs-style content marketing on 1-person budget; Product Hunt launches; AppSumo lifetime deals tradeoffs; cold email outreach; Twitter/X building in public; IndieHackers community distribution; integration marketplaces Shopify/WordPress/Zapier/Slack app directories as channels; affiliate programs; content marketing at scale-of-one); (d) pricing and monetization (SaaS pricing psychology Patel/Campbell; freemium vs free trial vs paid-only; per-seat vs usage-based vs flat-rate; annual discount strategies; grandfathering existing customers; churn reduction for micro-SaaS — Baremetrics/ProfitWell/ChartMogul analytics; MRR/ARR/LTV/CAC at micro scale; the $10K MRR milestone psychology); (e) solo founder mental model and lifestyle design (default alive vs default dead Graham; ramen profitability Levels; lifestyle business vs growth business spectrum; burnout prevention for solo operators — no team to delegate to; time management and context-switching costs; geographic arbitrage and remote-first; the 'build once sell twice' asset mindset; community as support network IndieHackers/WIP/MicroConf); (f) legal and operational basics (incorporation LLC/Ltd/Gm

日本語の概要は準備中です。原文の説明を表示しています。

Deploy to VPS. Code is already on the server. Start the service, configure nginx, verify accessible.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate the installation and management of VPS solutions using the Setup Automatik engine (powered by Orion Design). Use when the user wants to install, configure, or manage tools like Traefik, Portainer, Chatwoot, N8N, and other open-source applications on a Linux VPS.

日本語の概要は準備中です。原文の説明を表示しています。

Install, configure, and manage 1-SEC — an open-source, all-in-one cybersecurity platform (16 modules, single binary) on Linux servers and VPS instances. Use when the user asks to secure a server, install security monitoring, set up intrusion detection, harden a VPS, protect an AI agent host, or deploy endpoint defense. Covers installation, setup, enforcement presets, module configuration, alert management, and ongoing security operations.

日本語の概要は準備中です。原文の説明を表示しています。

Deep knowledge about deploying applications to Baremetal servers or Virtual Private Servers (VPS) using SSH, SCP, Rsync, and PM2/Systemd.

日本語の概要は準備中です。原文の説明を表示しています。

DevOps infra v2 — VPS, Docker, Coolify, CI/CD, monitoring, Tailscale

日本語の概要は準備中です。原文の説明を表示しています。

DevOps & Infrastructure IA — Gère le VPS, Docker, déploiements, monitoring, sécurité, tunnels Cloudflare. Expert Hetzner + Coolify + self-hosting.

日本語の概要は準備中です。原文の説明を表示しています。

Complete VPN server setup from scratch. Takes a fresh VPS (IP + root + password from hosting provider) through full server hardening and 3x-ui (Xray proxy panel) installation with VLESS Reality or VLESS TLS. Guides user through connecting via Hiddify client. Use when user mentions v2ray, xray, vless, 3x-ui, proxy server, vpn server, or wants to set up encrypted proxy access on a VPS. Designed for beginners — hand-holds through every step.

日本語の概要は準備中です。原文の説明を表示しています。

ConoHa VPS3 CLIによるインフラ構築スキル。サーバー作成、アプリデプロイ、 Kubernetesクラスター、OpenStackプラットフォーム、Slurmクラスターの構築を支援。 「ConoHaでサーバーを作って」「k8sクラスターを構築して」「アプリをデプロイして」 などのリクエストでトリガー。

Install, configure, and manage 1-SEC — an open-source, all-in-one cybersecurity platform (16 modules, single binary) on Linux servers and VPS instances. Use when the user asks to secure a server, install security monitoring, set up intrusion detection, harden a VPS, protect an AI agent host, or deploy endpoint defense. Covers installation, setup, enforcement presets, module configuration, alert management, and ongoing security operations.

日本語の概要は準備中です。原文の説明を表示しています。

Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, set up, provision, or deploy n8n on their own server/VPS/box (Hetzner, DigitalOcean, AWS EC2, bare metal, etc.) — in either single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance. This is for SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect the domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "install n8n on my server", "n8n docker compose", "n8n queue mode / workers / scaling", "n8n reverse proxy / SSL", "back up / update my n8n", or "we don't want to give every user the OAuth client secret" / "enable the Sign in with Google button" (credential overwrites).

日本語の概要は準備中です。原文の説明を表示しています。

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.

日本語の概要は準備中です。原文の説明を表示しています。

Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, provision, or deploy n8n on their own server/VPS (Hetzner, DigitalOcean, AWS EC2, bare metal) — single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance, or make Python Code nodes run on it (task runners). For SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "n8n docker compose", "n8n queue mode / workers", "n8n reverse proxy / SSL", "back up / update my n8n", "Python runner unavailable" / "n8nio/runners sidecar", or "we don't want to give every user the OAuth client secret" / "enable Sign in with Google" (credential overwrites).

日本語の概要は準備中です。原文の説明を表示しています。

星火燎原：从零起步、资源极少时，先评估客观条件，选定一个能站稳、能复用、能扩展的"根据地"（最小切入点），扎根后再逐步扩张，拒绝四处出击的流寇主义。当启动新项目、做 MVP / pilot、面对宏大目标不知从何下手、或做了很多零散事却没有积累时触发；项目已有稳固基础、只是修改现有系统时不触发。 English: Spark a prairie fire. When starting from almost nothing, assess the conditions, choose one base area (a minimal foothold that can hold, be reused, and expand), dig in, then grow step by step instead of scattering effort. Trigger for new projects, MVPs, pilots, daunting goals with no obvious first step, or busy work that accumulates nothing; skip when a solid base already exists or the task modifies an existing system.

日本語の概要は準備中です。原文の説明を表示しています。

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.

日本語の概要は準備中です。原文の説明を表示しています。

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

日本語の概要は準備中です。原文の説明を表示しています。

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test.

日本語の概要は準備中です。原文の説明を表示しています。