A command-line tool to send a message to devices via Pushbullet.
The command "bullet" requires the access token to call Pushbullet API. Execute the following command and register your access token:
$ bullet authThe access token is stored in a config file.
The default path of config file is $HOME/.config.bullet.
If you want to specify the path, use -c option:
$ bullet auth -c <path to the config file>Send a message to your devices via Pushbullet with the following command:
$ bullet send -t <title> -m <message>You can send a link or a file with the message:
$ bullet send -t <title> -m <message> -l <url or path>If you want to notify the specific device, use -d option with its nickname:
$ bullet send -d <nickname> -t <title> -m <message>The registered devices can be listed with bullet list.
If you are an OSX user, you can install "bullet" with Homebrew:
brew tap mitsuse/bullet
brew install bullet-cmdThe PKGBUILD file is available on AUR.
For other platform, the executable binaries are downloadable from the release page.
In the case of building from the sources, try the following:
$ go get -u github.com/mitsuse/bulletThe MIT License (MIT)
Copyright (c) 2015 Tomoya Kose.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.