Deployment overview
Automate deployments and execute commands across multiple servers simultaneously. Perfect for CI/CD pipelines and infrastructure automation.
What you can do
API-based deployment
Integrate Alpacon with your CI/CD pipelines using API access tokens with scoped permissions. Execute commands, transfer files, and manage servers programmatically.
Common use cases:
- GitHub Actions workflows
- GitLab CI/CD pipelines
- Jenkins jobs
- Custom deployment scripts
Multi-server command execution
Run commands across one or more servers from the Alpacon CLI using a work session with the Execute commands feature. Perfect for rolling updates, configuration changes, and batch operations.
Use cases:
- Deploy code to multiple servers
- Update configurations across your fleet
- Run maintenance scripts
- Execute health checks
See Session features and the alpacon exec reference.
Getting started
Tokens
Create and manage tokens for programmatic API access and automated server registration.
Multi-server commands
Request a work session with the Execute commands feature, then run alpacon exec from the CLI.
Integration guides
Looking to integrate with your CI/CD tools? Check out these guides:
Security considerations
API token security:
- Store tokens as encrypted secrets in your CI/CD platform
- Use separate tokens for different environments
- Rotate tokens regularly
- Revoke tokens when no longer needed
Multi-server command best practices:
- Test commands on staging servers first
- Monitor execution logs
- Implement rollback procedures
Related documentation
- Monitoring command history - Track all executed commands
- Access control - Manage deployment permissions
- Server groups - Organize servers for targeted deployments