Esther Olatunde esteedqueen

Woo! :D

Redis Cloud is a fully-managed service for running your Redis dataset. You can quickly and easily get your apps up and running with Redis Cloud through its add-on for Heroku, just tell us how much memory you need and get started instantly with your first Redis database. You can then add as many Redis databases as you need (each running in a dedicated process, in a non-blocking manner) and increase or decrease the memory size of your plan without affecting your existing data. You can easily import an existing dataset to any of your Redis Cloud databases, from your S3 account or from any other Redis server. Daily backups are performed automatically and in addition, you can backup your dataset manually at any given time.

Getting started

Start by installing the add-on:

:::term

$ heroku addons:add rediscloud

Mac Homebrew (RVM/MySQL/Redis) setup

Follow the steps below to setup a local development environment:

XQuartz

Recommended to download latest XQuartz

iTerm2

If you start to see something like this, e.g. on Heroku since they installed the postgres 9.5 client libraries on their dynos

/usr/lib/postgresql/9.5/bin/pg_dump: invalid option -- 'i'
Try "pg_dump --help" for more information.
rake aborted!
Error dumping database
/app/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.4/lib/active_record/tasks/postgresql_database_tasks.rb:55:in `structure_dump'

Setting up and installing rbenv, ruby-build, rubies, rbenv-gemset, and bundler

This guide enables you to install (ruby-build) and use (rbenv) multiple versions of ruby, isolate project gems (gemsets and/or bundler), and automatically use appropriate combinations of rubies and gems.

TL;DR Demo

# Ensure system is in ship-shape.

aptitude install git zsh libssl-dev zlib1g-dev libreadline-dev libyaml-dev

This guide assumes that you recently run brew upgrade postgresql and discovered to your dismay that you accidentally bumped from one major version to another: say 9.3.x to 9.4.x. Yes, that is a major version bump in PG land.

First let's check something.

brew info postgresql

The top of what gets printed as a result is the most important:

	module Authenticable

	# Devise methods overwrite
	def current_user
	@current_user \|\|= User.find_by(authentication_token: request.headers['Authorization'])
	end

	def authenticate_with_token!
	render json: { errors: "Not authenticated" },
	status: :unauthorized unless user_signed_in?

	# Call scopes directly from your URL params:
	#
	# @products = Product.filter(params.slice(:status, :location, :starts_with))
	module Filterable
	extend ActiveSupport::Concern

	module ClassMethods

	# Call the class methods with the same name as the keys in <tt>filtering_params</tt>
	# with their associated values. Most useful for calling named scopes from

	# Doesn't work
	<p>
	<% case @request.author_hosted %>
	<% when "yes" %>
	The school <b>has</b> hosted an author before.
	<% when "no" %>
	The school <b>has not</b> hosted an author before.
	<% end %>
	</p>

	gem 'devise'
	gem 'omniauth-facebook'