gistfile1.txt

source "http://rubygems.org"

# Declare your gem's dependencies in mxit-rails.gemspec.
# Bundler will treat runtime dependencies like base dependencies, and
# development dependencies will be added by default to the :development group.
gemspec

gem "surveyor"

#require 'mongo'
#source 'http://gemcutter.org'

gem 'rails', '3.2.8'

gem 'mysql2'

gem 'mysql2psql'

#gem "mongo_mapper"

gem 'heroku'

gem 'bcrypt-ruby', '~> 3.0.0'

=begin
# Using sqlite for development.  Obviously not a great idea in the real world
group :development, :test do
 gem 'pg'
 #gem 'activerecord-mysql2-adapter'
end
group :production do
  gem 'pg'
end

=end

# Gems used only for assets and not required
# in production environments by default.
group :assets do
  gem 'sass-rails',   '~> 3.2.3'
  gem 'coffee-rails', '~> 3.2.1'

  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
  # gem 'therubyracer', :platforms => :ruby

  gem 'uglifier', '>= 1.0.3'
end

#gem 'jquery-rails'
gem 'cloudfoundry-jquery-rails'

#gem 'mxit-rails'

# To use ActiveModel has_secure_password
# gem 'bcrypt-ruby', '~> 3.0.0'

# To use Jbuilder templates for JSON
# gem 'jbuilder'

gem 'thin'

# Deploy with Capistrano
# gem 'capistrano'

# To use debugger
# gem 'debugger'

# Declare any dependencies that are still in development here instead of in
# your gemspec. These might include edge Rails or gems from your path or
# Git. Remember to move these dependencies to your gemspec before releasing
# your gem to rubygems.org.

# To use debugger
# gem 'ruby-debug19', :require => 'ruby-debug'

ruby "2.0.0"