CLI client for haste-server
Go to file
Filipe Chagas 83052b3504 Upgrade version 2023-02-02 11:44:01 -03:00
.bundle update ga test workflow 2023-01-31 11:15:10 +03:00
.github update ga test workflow 2023-01-31 11:15:10 +03:00
bin Remove bundler/setup 2014-11-01 10:22:40 -04:00
lib Upgrade version 2023-02-02 11:44:01 -03:00
spec [UTI-2583] Adapt haste-client to the new API usage rules (#57) 2023-01-30 22:04:28 -03:00
.gitignore [UTI-2583] Adapt haste-client to the new API usage rules (#57) 2023-01-30 22:04:28 -03:00
.travis.yml Update travis to reflect rubies actually used in the real world 2017-07-19 17:30:45 -04:00
Gemfile Remove transpec dependency 2017-07-19 17:27:06 -04:00
LICENSE.txt [UTI-2583] Adapt haste-client to the new API usage rules (#57) 2023-01-30 22:04:28 -03:00 Fix licence link 2023-01-31 10:21:32 +03:00
Rakefile Update specs & fix Rakefile 2014-11-01 10:31:58 -04:00 Fix up TODO 2011-11-28 20:57:35 -05:00
haste.gemspec Upgrade version 2023-02-02 11:44:01 -03:00

Haste Client

Haste-client is a simple client for uploading data to Haste server. All you need to do is to pipe data in STDIN:

cat file | HASTE_SERVER_TOKEN=mytoken haste

And once the output makes it to the server, it will print the Haste share page URL to STDOUT.

This can be combined with pbcopy, like:

  • mac osx: cat file | haste | pbcopy
  • linux: cat file | haste | xsel

after which the contents of file will be accessible at a URL which has been copied to your pasteboard.


gem install haste


Most of the configuration is controlled by env variables. Here is the all environment variables that you can use.

HASTE_SERVER: Haste server domain url
HASTE_SERVER_TOKEN: Github authentication token
HASTE_SHARE_SERVER: Haste share server domain url
HASTE_USER: Basic authentication user name
HASTE_PASS: Basic authentication user pass

To add these environment variables, you should simply add them to your ~.bash_profile:

export VARIABLE="value"


If you are using default HASTE_SERVER, you need to have an GitHub authentication token. You can get the information about authentication and how to generate token here

After you have generated your token, you should add it to your ~.bash_profile:

export HASTE_SERVER_TOKEN="mytoken"

or you can add token to your command:

cat file | HASTE_SERVER_TOKEN=mytoken haste`

If your Haste installation requires http authentication, add the following to your ~.bash_profile:

export HASTE_USER="myusername"
export HASTE_PASS="mypassword"

if you are using SSL, you will need to supply your certs path

export HASTE_SSL_CERTS="/System/Library/OpenSSL/certs"


If you supply a valid file path as an argument to the client, it will be uploaded:

# equivalent
cat file | haste
haste file

Different Haste server

By default, Haste share page will point at If you have haste-server configured to serve bins on a separate domain, you also need to set ENV['HASTE_SHARE_SERVER'] value to that domain.

To set the value of share server, you can add the following to your ~.bash_profile:

export HASTE_SHARE_SERVER="myshareserver"

Different Haste server

By default, haste server will point at You can change this by setting the value of ENV['HASTE_SERVER'] to the URL of your Haste server.

To set the value of server, you can add the following to your ~.bash_profile:

export HASTE_SERVER="myserver"

Use with alias

You can also use alias to make easy shortcuts if you commonly use a few hastes intermingled with each other. To do that, you'd put something like this into ~.bash_profile:

alias work_haste="HASTE_SERVER= HASTE_SERVER_TOKEN=mytoken haste"


alias work_haste="HASTE_SERVER_TOKEN=mytoken haste"

After which you can use work_haste to send hastes to that server or with different tokens instead.

Use as a library

You can also use Haste as a library to upload hastes:

require 'haste'
uploader =
uploader.upload_raw 'this is my data' # key
uploader.upload_path '/tmp/whaaaa' # key

Contributor License Agreement

Licensed under the MIT license.