Releases: micro/go-micro
Releases · micro/go-micro
v5.13.0 - Deployment Support
What's New
Seamless Deployment to Linux Servers
Deploy your services to any Linux server with systemd:
# One-time server setup
ssh user@server
curl -fsSL https://go-micro.dev/install.sh | sh
sudo micro init --server
# Deploy from your laptop
micro deploy user@serverNew Commands
- micro init --server - Initialize a server to receive deployments
- micro deploy - Deploy services via SSH + systemd
- micro status --remote - Check service status on remote servers
- micro logs --remote - Stream logs from remote servers
- micro stop --remote - Stop services on remote servers
Configuration
Named deploy targets in micro.mu:
deploy prod
ssh [email protected]
deploy staging
ssh [email protected]
Then: micro deploy prod
Philosophy
- systemd is the process supervisor (battle-tested)
- SSH is the transport (no custom agents)
- No platform needed (unlike Micro v3)
- Helpful error messages guide you through setup
See docs/deployment.md for the full guide.
Full Changelog
v5.12.0
docs: clarify gRPC server option ordering and service name usage (#2820) * Initial plan * docs: clarify gRPC server option ordering and service name usage - Fix all examples to show Server option before Name option - Add note explaining why option ordering matters - Add new section on "Option Ordering Issue" in Common Errors - Add new section on "Service Name vs Package Name" in Common Errors - Update transport.md to show proper ordering with comment Co-authored-by: asim <[email protected]> * docs: refine comments based on code review feedback - Clarify that Server ordering before Name is mandatory - Remove confusing comment about Client ordering being for consistency Co-authored-by: asim <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: asim <[email protected]>