Skip to content
Store entire documents in URLs
CoffeeScript CSS Ruby HTML Makefile
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets Change url to marked repo Aug 2, 2018
extras use HTTPS Feb 28, 2019
images remove broken QR codes Aug 6, 2017
src use HTTPS Feb 28, 2019
.gitignore improve build process Dec 22, 2013
.npmrc use HTTPS Feb 28, 2019
LICENSE Cakefile: add a task for running Hashify locally, and one for bundlin… Dec 14, 2013
Makefile update width of tweet button Aug 6, 2017
README.md use HTTPS Feb 28, 2019
nginx.conf.default use HTTPS Feb 28, 2019
package.json use HTTPS Feb 28, 2019

README.md

Hashify

Hashify does not solve a problem, it poses a question: what becomes possible when one is able to store entire documents in URLs?

Installation

  1. Install rbenv.

  2. Install dependencies:

    make setup
    
  3. Build:

    make
    
  4. Install nginx.

  5. Create a symlink to nginx.conf from wherever nginx sites live. For example:

    ln -s "$(pwd)/nginx.conf" /opt/local/etc/nginx/sites-available/hashify.me
    
  6. Activate the site if necessary. For example:

    ln -s ../sites-available/hashify.me /opt/local/etc/nginx/sites-enabled/hashify.me
    
  7. Reload nginx:

    sudo nginx -s reload
    

localhost

Hashify uses CORS in its communication with bitly. Though browsers don't allow this on localhost, one can use https://lvh.me for testing (lvh.me resolves to localhost).

You can’t perform that action at this time.