This gem provides a CLI and an API interface to http://pushover.net
It's main usage as a CLI, see below for specifics.
Some CLI features:
- Multiple users/applications can be stored.
- Do not need to supply either, will find the first one available.
- Supplying on the CLI will always override the stored variables.
$ gem install pushover
To use inside of an application, add this to the your gemfile:
$ gem 'pushover'
and run bundle to make it available:
To send with the very minimum amount of information.
.('message', 'title', user:'USER_TOKEN', token:'APP_TOKEN')
Optional #configuration method:
. do |config| config.user='USER_TOKEN' config.token='APP_TOKEN' end .('message', 'title')
To send a message. This will override any saved information available.
$ pushover -u user_token -a app_key message is the rest of the cli.
You can also save and use stored information. The username/application are titles. They can be anything you want to reference them.
$ pushover -u user_token --save-user username
$ pushover -a app_key --save-user application
This will allow you to do:
$ pushover -a new_app -u username message body.
If you don't supply any credentials, and it has them saved, it will use the first set saved. This allows for a completely lazy mode
pushover message body here for sending without having to constantly specify credentials.
Delete coming soon.
Testing, like this utility, it is a work in progress. I'm in the process of lifting some of the code into another library (config, options), so I will likely not be making more tests for those pieces.
The app testing itself requires you to use your own credentials, that way you get the spam from pushover and not me. I haven't figured out how to do this just yet.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Added some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request