Contents

<img src="http://lockupgem.com/github_host/lockup_mark.png" width="100" height="134" alt="Lockup Shield" />

# Lockup

[![Gem Version](https://badge.fury.io/rb/lockup.png)](http://badge.fury.io/rb/lockup)

A simple gem to more elegantly place a staging server or other in-progress rails application behind a basic codeword. It’s easy to implement, share with clients/collaborators, and more beautiful than the typical password-protection sheet.

_“Can I come into your fort?”_

_“…what's the codeword?”_

(currently used in production with Rails 3.X and nonimally tested—seems to work—in Rails 4)

## Installation

1. Add this line to your application's Gemfile:

        gem 'lockup'

2. Define a codeword (see Usage below).

3. Mount the engine in your application's routes file (usually first, for best results):

        mount Lockup::Engine, at: '/lockup'

## Usage

To set a codeword, define LOCKUP_CODEWORD in your environments/your_environment.rb file like so:

    ENV["LOCKUP_CODEWORD"] = 'secret'

If you think you might need a hint:

    ENV["LOCKUP_HINT"] = 'Something that you do not tell everyone.'

If you're using [Figaro](https://github.com/laserlemon/figaro), set your lockup codeword and hint (optional) in your application.yml file:

    LOCKUP_CODEWORD: "love"

    LOCKUP_HINT: "Pepé Le Pew"

**Codewords are not case-sensitive, by design. Keep it simple.**

### Link it with no typing:

    http://somedomain.com/or_path/?lockup_codeword=love

The visitor is redirected and the cookie is set without them ever seeing the Lockup splash page.

(Lockup also makes a rudimentary attempt based on user agent to **block major search engine bots/crawlers** from following this link and indexing the site, just in case it ever gets out into the wild.)

## Contribute

Pull requests are welcome, but please make them to the _development_ branch.

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
lockup-1.2.0	README.md