ostent displays current system metrics. Demo here
Install & run with curl -sSL https://github.com/ostrost/ostent/raw/master/ostent.sh | sh
It's a single executable without dependecies. Once installed, it will self-upgrade whenever there's new release.
Binaries distributed by GitHub Releases
ostent accepts optional -bind argument to set specific IP and/or port to bind to, otherwise any machine IP and port 8050 by default.
ostent -bind 127.1# http://127.0.0.1:8050/ostent -bind 192.168.1.10:8051# port 8051ostent -bind 8052# any IP, port 8052
-update sets collection interval (1 second by default), append s for seconds, m for minutes: 5s, 1m etc.
Run it, it'll give the link(s) to open in a browser.
-
git clone https://github.com/ostrost/ostent.gitIf you've cloned (or forked) the repo while it was github.com/rzab/ostent please check the output of
git remote -v. For any remote names (e.g. origin or upstream) pointing to the old location set it to the new:git remote set-url origin https://github.com/ostrost/ostent.gitfor theoriginetc. -
cd ostent -
export GOPATH=${GOPATH:-$PWD}:$PWD PATH=$PATH:$PWD/binAdds ./ to GOPATH and ./bin to PATH.
-
make bootstrap- installs required Go packages
- generates
src/share/{assets,templates}/bindata.devel.goThese files will contain absolute local paths.
-
Either
maketo build orrerunostentfor live-reloading run.
[src/]ostent is the main (as in Go Program execution) package:
rerun will find main.devel.go file; the other main.production.go (used when building with -tags production)
is the init code for the distributed binaries: also includes
goagain recovering and self-upgrading via go-update.
[src/]amberp/amberpp is templates compiler, used with make.
GNU make to rebuild the assets and build the program.
Additional required tools here:
- Sass
- react-tools
- uglify-js (for builds)
make rebuilds these commited to the repo files:
src/share/templates/bindata.production.gosrc/share/assets/bindata.production.gosrc/share/assets/js/devel/milk/*.jssrc/share/assets/js/devel/gen/*.jssrc/share/templates/*.htmlsrc/share/assets/css/*.csssrc/share/tmp/jsassets.dsrc/share/tmp/*.jsx
If you don't change source files, content re-generated should not differ from the commited.
Whenever src/share/{amber.templates,style,coffee} modified, you have to re-run make.
make compiles everything and produces final binary.
The binaries, to be stand-alone, have the assets and templates embeded.
Unless you specifically go build with -tags production (e.g with make),
the content is not embeded for the ease of development:
with rerun ostent, asset requests are served from the actual files.