Scaleway 一键部署技能 - 无需 DevOps 知识，3分钟自动配置 VPS 服务器

Scaleway Deployment by clementwalter/claudine

1 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/clementwalter/claudine --skill 'Scaleway Deployment'

自动化云服务开发运维

🇨🇳中文介绍

Scaleway 部署技能

理念：无需 DevOps 知识

用户不懂 DevOps。用户也不想知道 DevOps。处理一切事务。

除非明确询问，否则不要解释基础设施概念
除非必要，不要展示 Terraform 文件、YAML 配置或命令输出
只询问你绝对无法自行弄清楚的事情
将所有凭证存储在 GitHub Secrets 中一次，不再询问
静默运行脚本，只显示成功/失败
当你必须询问某事时，要像对五岁孩子解释一样简单明了

当用户说"部署一个 VPS"或"部署到 Scaleway"时

步骤 1：询问服务器名称

始终询问："你想怎么称呼这个服务器？"

此名称将用于：

Scaleway 上的服务器主机名
SSH 配置别名（以便用户可以 ssh root@<名称>）

步骤 2：检查凭证是否已设置

检查 Scaleway CLI 是否已配置：scw config dump

如果未配置，逐个询问凭证：

问题 1：Scaleway 账户

我需要连接到你的 Scaleway 账户。以下是获取密钥的方法：

访问 https://console.scaleway.com/iam/api-keys

点击"生成 API 密钥"

复制"访问密钥"（以"SCW"开头）

复制"密钥"（长随机字符串）

广告位招租

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

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

联系我们

步骤 3：创建服务器并配置 SSH

创建服务器后：

创建非 root 用户（许多工具拒绝以 root 身份运行）：

ssh root@<IP> << 'EOF'
# 创建具有 sudo 和 docker 访问权限的用户
useradd -m -s /bin/zsh <用户名>
echo "<用户名> ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/<用户名>
usermod -aG sudo,docker <用户名>

# 复制 SSH 密钥
mkdir -p /home/<用户名>/.ssh
cp /root/.ssh/authorized_keys /home/<用户名>/.ssh/
chown -R <用户名>:<用户名> /home/<用户名>/.ssh
chmod 700 /home/<用户名>/.ssh
chmod 600 /home/<用户名>/.ssh/authorized_keys
EOF

使用本地用户名（来自 whoami）作为 <用户名>。

将条目添加到 ~/.ssh/config（使用非 root 用户）：

Host <名称>
    HostName <IP地址>
    User <用户名>
    IdentityFile ~/.ssh/id_ed25519

缓存 IP：echo "<IP>" > ~/.cache/scaleway-deploy/<名称>_ip
同步用户的 shell 环境（使服务器感觉像本地一样）：

# 安装 zsh（首先以 root 身份，在用户设置之前）
ssh root@<IP> "apt-get install -y -qq zsh git"

# 为用户安装 oh-my-zsh
ssh <名称> 'sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" "" --unattended'

# 安装常用插件
ssh <名称> 'git clone https://github.com/zsh-users/zsh-autosuggestions ~/.oh-my-zsh/custom/plugins/zsh-autosuggestions; git clone https://github.com/zsh-users/zsh-syntax-highlighting ~/.oh-my-zsh/custom/plugins/zsh-syntax-highlighting'

# 复制用户的配置
scp ~/.zshrc <名称>:~/.zshrc
scp ~/.gitconfig <名称>:~/.gitconfig

# 重要：使 .zshrc 可移植（修复硬编码路径和缺失的工具）
ssh <名称> << 'FIXZSH'
# 修复硬编码的主目录路径
sed -i "s|/Users/[^/]*/|$HOME/|g" ~/.zshrc
sed -i "s|/opt/homebrew/[^\"]*|$HOME/.local/bin|g" ~/.zshrc

# 用存在性检查包装可选工具
sed -i 's|^\. \$HOME/.asdf/asdf.sh|[ -f "$HOME/.asdf/asdf.sh" ] \&\& . "$HOME/.asdf/asdf.sh"|' ~/.zshrc
sed -i 's|^\. "\$HOME/.atuin/bin/env"|[ -f "$HOME/.atuin/bin/env" ] \&\& . "$HOME/.atuin/bin/env"|' ~/.zshrc
sed -i 's|^eval "\$(atuin init zsh)"|command -v atuin \&>/dev/null \&\& eval "$(atuin init zsh)"|' ~/.zshrc
sed -i 's|^eval "\$(scw autocomplete script shell=zsh)"|command -v scw \&>/dev/null \&\& eval "$(scw autocomplete script shell=zsh)"|' ~/.zshrc

# 用存在性检查包装 nvm/load-nvmrc（如果未安装 nvm 则注释掉）
if ! command -v nvm &>/dev/null; then
  sed -i '/^load-nvmrc() {/,/^}$/s/^/# /' ~/.zshrc
  sed -i 's/^add-zsh-hook chpwd load-nvmrc/# add-zsh-hook chpwd load-nvmrc/' ~/.zshrc
  sed -i '/^load-nvmrc$/s/^/# /' ~/.zshrc
fi
FIXZSH

告诉用户："完成！使用以下命令连接：ssh <名称>"

步骤 4：部署应用（如果请求）

自动运行部署。告诉用户：

"正在部署你的应用...完成！你的应用已上线，地址为：http://（或 http://IP）"

脚本参考（供 Claude 使用，非用户）

脚本	用途
`scripts/setup.py`	一次性设置，将密钥存储在 GitHub 中
`scripts/deploy.py`	部署应用（使用 `--auto` 标志进行静默模式）
`scripts/status.py`	检查一切是否正常运行
`scripts/logs.py`	如果出现问题，获取应用日志
`scripts/destroy.py`	销毁一切（务必先询问用户确认！）

"完成！你的应用已上线，地址为 http://X.X.X.X"

"出了点问题。让我检查一下... [运行 logs.py，诊断，如果可能自动修复 > > > > > >]"

如果用户询问技术问题

简要回答，然后主动提出处理：

"那是[简要解释]。需要我直接为你设置吗？"

合规性（对用户不可见）

所有这些都自动发生，用户永远看不到：

SOC2/ISO27001 控制已嵌入每个模板
加密卷、防火墙、审计日志 - 全部自动完成
合规性验证在每次部署后静默运行
如果合规性失败，自动修复，不打扰用户

GitHub Secrets 存储

将这些密钥存储在用户的 GitHub 仓库中（仅一次）：

密钥名称	值
`SCW_ACCESS_KEY`	Scaleway 访问密钥
`SCW_SECRET_KEY`	Scaleway 密钥
`SCW_PROJECT_ID`	Scaleway 项目 ID
`SCW_SSH_PRIVATE_KEY`	自动生成的 SSH 私钥
`SCW_SSH_PUBLIC_KEY`	自动生成的 SSH 公钥
`SCW_SERVER_IP`	服务器 IP（配置后）

Claude 的快速命令

# 检查设置是否完成
uv run .claude/skills/scaleway-dev/scripts/setup.py --check

# 运行完整设置（交互式，询问凭证）
uv run .claude/skills/scaleway-dev/scripts/setup.py

# 部署（静默模式）
uv run .claude/skills/scaleway-dev/scripts/deploy.py --auto

# 检查状态
uv run .claude/skills/scaleway-dev/scripts/status.py

# 查看日志
uv run .claude/skills/scaleway-dev/scripts/logs.py --tail 50

# 销毁一切（务必先询问用户！）
uv run .claude/skills/scaleway-dev/scripts/destroy.py

永远不要向用户展示基础设施代码
永远不要解释 Terraform/Docker/cloud-init 是什么
永远不要询问区域、实例类型或技术选择
始终使用合理的默认值（fr-par, DEV1-S, Ubuntu 22.04）
始终将凭证存储在 GitHub Secrets 中
始终静默运行合规性检查
只告诉用户："正在设置..." / "正在部署..." / "完成！"

无服务器容器（推荐用于应用）

有关何时使用无服务器容器与 VPS，请参见上面的部署策略部分。快速参考：scw container container create 和 scw container container deploy。

🇺🇸English

Scaleway Deployment Skill

Philosophy: Zero DevOps Knowledge Required

The user doesn't know DevOps. The user doesn't WANT to know DevOps. Handle everything.

Do NOT explain infrastructure concepts unless explicitly asked
Do NOT show Terraform files, YAML configs, or command outputs unless necessary
Ask ONLY what you absolutely cannot figure out yourself
Store ALL credentials in GitHub Secrets once, never ask again
Run scripts silently, only show success/failure
When you MUST ask something, be ELI5 (Explain Like I'm 5)

When User Says "Deploy a VPS" or "Deploy to Scaleway"

Step 1: Ask for Server Name

Always ask: "What do you want to call this server?"

This name will be used for:

The server hostname on Scaleway
The SSH config alias (so user can ssh root@<name>)

Step 2: Check if Credentials Set Up

Check if Scaleway CLI is configured: scw config dump

If not configured, ask for credentials ONE AT A TIME:

Question 1: Scaleway Account

I need to connect to your Scaleway account. Here's how to get the keys:

Go to https://console.scaleway.com/iam/api-keys

Click "Generate API Key"

Copy the "Access Key" (starts with "SCW")

Copy the "Secret Key" (long random string)

Paste them here (I'll store them securely in GitHub, you won't need them again):

Access Key: Secret Key:

Question 2: Scaleway Project

Now I need your Project ID:

Go to https://console.scaleway.com/project/settings

Copy the "Project ID" (looks like: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

Paste it here:

That's it. Run uv run .claude/skills/scaleway-dev/scripts/setup.py to:

Store credentials in GitHub Secrets
Generate SSH keys automatically
Create the server
Set up everything else

Tell the user: "Setting up your server... This takes about 3 minutes."

Step 3: Create Server and Configure SSH

After creating the server:

Create non-root user (many tools refuse to run as root):

ssh root@<IP> << 'EOF'

# Create user with sudo and docker access
useradd -m -s /bin/zsh <username>
echo "<username> ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/<username>
usermod -aG sudo,docker <username>

# Copy SSH keys
mkdir -p /home/<username>/.ssh
cp /root/.ssh/authorized_keys /home/<username>/.ssh/
chown -R <username>:<username> /home/<username>/.ssh
chmod 700 /home/<username>/.ssh
chmod 600 /home/<username>/.ssh/authorized_keys
EOF

Use the local username (from whoami) as <username>.

Add entry to ~/.ssh/config (with non-root user):

Host <name>

    HostName <IP_ADDRESS>
    User <username>
    IdentityFile ~/.ssh/id_ed25519

3. Cache the IP: echo "<IP>" > ~/.cache/scaleway-deploy/<name>_ip

Sync user's shell environment (so server feels like local):

# Install zsh (as root first, before user setup)

ssh root@<IP> "apt-get install -y -qq zsh git"

# Install oh-my-zsh for the user
ssh <name> 'sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" "" --unattended'

# Install common plugins
ssh <name> 'git clone https://github.com/zsh-users/zsh-autosuggestions ~/.oh-my-zsh/custom/plugins/zsh-autosuggestions; git clone https://github.com/zsh-users/zsh-syntax-highlighting ~/.oh-my-zsh/custom/plugins/zsh-syntax-highlighting'

# Copy user's configs
scp ~/.zshrc <name>:~/.zshrc
scp ~/.gitconfig <name>:~/.gitconfig

# IMPORTANT: Make .zshrc portable (fix hardcoded paths and missing tools)
ssh <name> << 'FIXZSH'
# Fix hardcoded home paths
sed -i "s|/Users/[^/]*/|$HOME/|g" ~/.zshrc
sed -i "s|/opt/homebrew/[^\"]*|$HOME/.local/bin|g" ~/.zshrc

# Wrap optional tools in existence checks
sed -i 's|^\. \$HOME/.asdf/asdf.sh|[ -f "$HOME/.asdf/asdf.sh" ] \&\& . "$HOME/.asdf/asdf.sh"|' ~/.zshrc
sed -i 's|^\. "\$HOME/.atuin/bin/env"|[ -f "$HOME/.atuin/bin/env" ] \&\& . "$HOME/.atuin/bin/env"|' ~/.zshrc
sed -i 's|^eval "\$(atuin init zsh)"|command -v atuin \&>/dev/null \&\& eval "$(atuin init zsh)"|' ~/.zshrc
sed -i 's|^eval "\$(scw autocomplete script shell=zsh)"|command -v scw \&>/dev/null \&\& eval "$(scw autocomplete script shell=zsh)"|' ~/.zshrc

# Wrap nvm/load-nvmrc in existence check (comment out if nvm not installed)
if ! command -v nvm &>/dev/null; then
  sed -i '/^load-nvmrc() {/,/^}$/s/^/# /' ~/.zshrc
  sed -i 's/^add-zsh-hook chpwd load-nvmrc/# add-zsh-hook chpwd load-nvmrc/' ~/.zshrc
  sed -i '/^load-nvmrc$/s/^/# /' ~/.zshrc
fi
FIXZSH

6. Tell user: "Done! Connect with:ssh <name>"

Step 4: Deploy App (if requested)

Run deployment automatically. Tell the user:

"Deploying your app... Done! Your app is live at: http:// (or http://IP)"

Scripts Reference (For Claude, Not User)

Script	Purpose
`scripts/setup.py`	One-time setup, stores secrets in GitHub
`scripts/deploy.py`	Deploy app (use `--auto` flag for silent mode)
`scripts/status.py`	Check if everything is running
`scripts/logs.py`	Get app logs if something is wrong
`scripts/destroy.py`	Tear down everything (ask for confirmation!)

What To Say To Users

On Success

"Done! Your app is live at http://X.X.X.X"

On Failure

"Something went wrong. Let me check... [run logs.py, diagnose, fix > > > > > >

automatically if possible]"

If User Asks Technical Questions

Answer briefly, then offer to just handle it:

"That's [brief explanation]. Want me to just set it up for you?"

Compliance (Invisible to User)

All this happens automatically, user never sees it:

SOC2/ISO27001 controls are baked into every template
Encrypted volumes, firewalls, audit logging - all automatic
Compliance verification runs silently after each deploy
If compliance fails, fix it automatically, don't bother the user

GitHub Secrets Storage

Store these secrets in the user's GitHub repo (one time only):

Secret Name	Value
`SCW_ACCESS_KEY`	Scaleway access key
`SCW_SECRET_KEY`	Scaleway secret key
`SCW_PROJECT_ID`	Scaleway project ID
`SCW_SSH_PRIVATE_KEY`	Auto-generated SSH private key
`SCW_SSH_PUBLIC_KEY`	Auto-generated SSH public key
`SCW_SERVER_IP`	Server IP (after provisioning)

Quick Commands For Claude

# Check if setup is done
uv run .claude/skills/scaleway-dev/scripts/setup.py --check

# Run full setup (interactive, asks for credentials)
uv run .claude/skills/scaleway-dev/scripts/setup.py

# Deploy (silent mode)
uv run .claude/skills/scaleway-dev/scripts/deploy.py --auto

# Check status
uv run .claude/skills/scaleway-dev/scripts/status.py

# View logs
uv run .claude/skills/scaleway-dev/scripts/logs.py --tail 50

# Destroy everything (ALWAYS ask user first!)
uv run .claude/skills/scaleway-dev/scripts/destroy.py

Remember

Never show infrastructure code to the user
Never explain what Terraform/Docker/cloud-init is
Never ask about regions, instance types, or technical choices
Always use sensible defaults (fr-par, DEV1-S, Ubuntu 22.04)
Always store credentials in GitHub Secrets
Always run compliance checks silently
Only tell the user: "Setting up..." / "Deploying..." / "Done!"

Serverless Containers (Recommended for Apps)

See the deployment strategy section above for when to use Serverless Containers vs VPS. Quick reference: scw container container create and scw container container deploy.

Weekly Installs

Repository

clementwalter/claudine

GitHub Stars

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubWarn SocketFail SnykFail

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

114,200 周安装