Rails%203%20In%20Action

Deploy away!
** [out :: [server]] -- create_table(:projects)
** [out :: [server]] -> 0.0012s
...
This indicates that the migrations have happened successfully. Unfortunately, this is in
the wrong database! You spent all that time setting up a PostgreSQL server and it’s
gone ahead and instead used SQLite3. The nerve!
14.5.6 Choosing a database
To fix this, you can make a little change to your application’s Gemfile. Rather than
having sqlite3 out there in the open and not in a group, switch it to only be used in
development and test by moving it down into the group :development, :test block
just underneath. 26 Beneath all of the content in the file currently, define a new group
like this:
group :production do
gem 'pg'
end
The pg gem provides the PostgreSQL adapter that you need to connect to your Postgre-
SQL database server on your server. If you run bundle install now it will install this
gem for you. Now you can make a commit for this small change and push your changes:
git add Gemfile*
git commit -m "Added pg gem for PostgreSQL on the server"
git push
You haven’t yet configured your production application to connect to PostgreSQL,
which is somewhat of a problem. You would usually do this by editing the config/database
.yml file in your application, but in this case you want to keep your development and production
environments separate. Therefore, you’ll set this up on the server.
Put this file in the shared directory of your application’s deploy, so that all releases
can just symlink it to config/database.yml inside the application itself. Connect to the
server now with your user and then switch over to ticketeeapp.com using sudo su
ticketeeapp.com so that you can add this file. Go into this shared directory now and
open a new file for editing by running these commands:
cd /home/ticketeapp.com/apps/ticketee/shared
mkdir config
cd config
nano database.yml
Inside this file, put the database settings for the production environment of your
application. These are as follows:
production:
adapter: postgresql
database: ticketeeapp.com
min_messages: warning
26 Generally, this is a bad idea. You should always develop on the same database system that you deploy on so
that you don’t run into any unexpected production issues. We’re being lazy here because it’s easier.
405