Install the Alpacon CLI in your GitHub Actions workflow — the first step for automating server management directly from CI/CD.

• Official documentation

• Zero SSH keys — Authenticate with API tokens instead of managing SSH keys across repos and servers
• One-line setup — A single step installs the CLI; no manual downloads or version pinning needed
• Idempotent — Skips installation if the CLI is already present, keeping workflows fast

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Alpacon CLI
        uses: alpacax/alpacon-setup-action@v1

      - name: Deploy application
        uses: alpacax/alpacon-websh-action@v1
        with:
          workspace-url: ${{ secrets.ALPACON_WORKSPACE_URL }}
          api-token: ${{ secrets.ALPACON_API_TOKEN }}
          target: 'prod-server'
          script: |
            cd /opt/myapp
            git pull
            npm install
            pm2 restart app

This action requires no inputs.

• ubuntu-latest (and other Ubuntu-based runners)

• alpacon-websh-action — Execute shell commands on remote servers
• alpacon-cp-action — Copy files to/from remote servers
• alpacon-common-action — Run any Alpacon CLI command

• GitHub Actions integration guide
• Alpacon CLI reference

When creating a new release, always update the v1 major version tag:

git tag -f v1 v1.x.0
git push origin v1 --force

This ensures users referencing @v1 automatically get the latest release.