iron-app extends [envconsul] with the following features, described details below.
- Service discovery
- Process logs hooks
- [TODO] Application performances storage
- [TODO] Application metadata storage in consul
go get github.com/hivetech/iron-app
Run iron-app to see the usage help:
$ iron-app
Usage: iron-app [options] prefix child...
Exoskeleton for applications.
Load env from Consul's K/V store, discover provided services, route
application output and store performances and application metadata.
Options:
-addr="127.0.0.1:8500": consul HTTP API address with port
-dc="": consul datacenter, uses local if blank
-discover="": Comma separated <service:tag> on the network to discover
-errexit=false: exit if there is an error watching config keys
-loghook="": An app where to send logs [pushbullet]
-reload=false: if set, restarts the process when config changes
-sanitize=true: turn invalid characters in the key into underscores
-upcase=true: make all environmental variable keys uppercase
-verbose=false: Extend log output to debug level
iron-app replicates the full possibilities of envconsul.
You can ask iron-app to automatically inject into process environment how to access a remote service, known by consul.
Considering an application registered in the console network under redis
service with a tag cache :
$ ./iron-app --discover redis:cache app/env env
...
INFO[0000] env REDIS_HOST=172.17.0.4
INFO[0000] env REDIS_PORT=80
INFO[0000] Done
iron-app outputs logs on stdout and stderr but it also comes with
built-in routines that ship them elsewhere :
- File -
--loghook anything.log - Hipchat - Export
HIPCHAT_API_KEYandHIPCHAT_ROOMand use--loghook hipchat - Pushbullet - Export
PUSHBULLET_API_KEYandPUSHBULLET_DEVICEand use--loghook pushbullet
Currently, hipchat and pushbullet catch only panic, fatal and error
levels as configured in log/hipchat.go and log/pushbullet.go.