jhubert

Overview

There can be a business or security requirement that certain fields on a model should never be exposed in an API. One approach to this is to tell the developers not to ever put the field in the API output, but I prefer to protect them at the model level because that's where the requirement actually is.

The goal of this is to have a simple way to specify fields that should be prevented from being exposed. This is one approach and I would love feedback both on the implementation and on the approach. Ideas and criticism are very welcome. :)

mrrooijen

Heroku SSL Endpoint

Assumptions:

• You want to enable SSL for your domain.
• You want to go with RapidSSL.
• Your domain name is www.domain.com during this example.
• You want to encrypt requests for a single domain (no wildcard)
• You want to apply this certificate to Heroku's SSL Endpoint

IanVaughan

#!/usr/bin/env bash

uninstall() {
  list=`gem list --no-versions`
  for gem in $list; do
    gem uninstall $gem -aIx
  done
  gem list
  gem install bundler
}

cblunt

# ...

gem 'carrierwave'
gem 'fog', '~> 1.0.0' # Need to specify version, as carrierwave references older (0.9.0) which doesn't allow configuration of Rackspace UK Auth URL

jhubert

We went out on the town last night
And drank to my friend's delight
i remember a shot
the rest i forgot
Lets do it again tonight!