hk create # create app
hk destroy # destroy app
hk apps # list apps
hk set # set config var
hk unset #unset config var
Compare to heroku's (preferable, imho) commands: heroku apps:create # create app
heroku apps:destroy # destroy app
heroku apps # list apps
heroku config:set # set config var
heroku config:unset # unset config var
The command 'hk set' doesn't tell you any semantic information at all about what it's doing - I prefer the original syntax for its convention of being explicit.
To allow / cause your site to break when analytics aren't served is, in essence, attempting to enforce an unspoken contract between gathering user info and serving them data.
As far as I'm concerned, a site that doesn't work when analytics aren't served is a site I will literally never use.