Skip to content

Commit

Permalink
Switched to pg for heroku deployment
Browse files Browse the repository at this point in the history
  • Loading branch information
byee01 committed Sep 11, 2011
1 parent ed59680 commit c9c6bc3
Show file tree
Hide file tree
Showing 3 changed files with 25 additions and 3 deletions.
10 changes: 8 additions & 2 deletions Gemfile
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,6 @@ gem 'rails', '3.1.0'
# Bundle edge Rails instead:
# gem 'rails', :git => 'git://github.com/rails/rails.git'

# Use postgres for database
gem 'pg'

# Gems used only for assets and not required
# in production environments by default.
Expand All @@ -19,6 +17,14 @@ gem 'therubyracer', :require => 'v8'
gem 'jquery-rails'

# Deploy with to Heroku for testing
# Use postgres for database as Heroku doesn't support sqlite3
group :production do
gem 'pg'
end

group :development do
gem 'sqlite3'
end

# To use debugger
# gem 'ruby-debug19', :require => 'ruby-debug'
Expand Down
2 changes: 2 additions & 0 deletions Gemfile.lock
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,7 @@ GEM
hike (~> 1.2)
rack (~> 1.0)
tilt (!= 1.3.0, ~> 1.1)
sqlite3 (1.3.4)
therubyracer (0.9.4)
libv8 (~> 3.3.10)
thor (0.14.6)
Expand All @@ -108,6 +109,7 @@ DEPENDENCIES
pg
rails (= 3.1.0)
sass-rails (~> 3.1.0)
sqlite3
therubyracer
turn
uglifier
16 changes: 15 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,18 @@
Teudu
---
===

This is the teudu webservice. It's based off of RoR 3.1.

Deploying
---

I don't know if we're ready for that yet...
You can push back to here by typing: `git push`

And to Heroku with: `git push heroku master`

Database
---

We test online with the app deployed to Heroku. Since Heroku uses Postgres instead of sqlite, you should run bundle install with the development context.
`bundle install --without production`

0 comments on commit c9c6bc3

Please sign in to comment.