mirror of https://github.com/statping/statping
Updated Deployment (markdown)
parent
95d3a6ef64
commit
4c51cbf33e
|
@ -1 +1,14 @@
|
||||||
# How Statup is Deployed
|
# How Statup is Deployed
|
||||||
|
Statup is a pretty cool server for monitoring your services. The way we deploy might be a little cooler though. Statup is using the most bleeding edge technology to release updates and distribute binary files automatically.
|
||||||
|
|
||||||
|
## Deployment Flow
|
||||||
|
Statup has a pretty advanced deployment process that many people will find to be a little too complexed. Below is a flow of how this application is developed and deployed.
|
||||||
|
|
||||||
|
- Source code commits get pushed to Github
|
||||||
|
- Travis-CI begins to build the binary application
|
||||||
|
- Go Language builds all binaries with xgo and Docker.
|
||||||
|
- New binaries are compress and released to Github Releases.
|
||||||
|
- Triggers a build on Docker Hub `latest` release, the version tag is triggered when tag is set.
|
||||||
|
- Triggers Travis build for Statup Homebrew repo to recreate the Formula for brew.
|
||||||
|
- Travis recreates statup.repo Formula and commits back to master.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue