Add production settings to database.yml

[swanson]

Heroku automatically writes these, but for VPS we need to set them up.

Also update instructions for VPS to make sure it is run in prod env - not dev.

[mickstephenson]

Since the user would have to edit the file manually to change the password and the correct user, perhaps merely explaining how to do this is the documentation would be enough.

[swanson]

Probably best to use ENV variables for this.

From: Michael Stephenson [mailto:notifications@github.com]
Sent: Friday, May 17, 2013 1:48 PM
To: swanson/stringer
Cc: Matthew D. Swanson
Subject: Re: [stringer] Add production settings to database.yml (#64)

Since the user would have to edit the file manually to change the password and the correct user, perhaps merely explaining how to do this is the documentation would be enough.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/64#issuecomment-18076058.

[mickstephenson]

Such as:

development:
  adapter: sqlite3
  database: db/stringer.sqlite

production:
  adapter:  postgresql
  database: $POSTGRES_DATABASE
  username: $POSTGRES_USER
  password: $POSTGRES_PASSWORD
  host: $POSTGRES_HOST

Then simply adding their definitions to .bash_profile as part of the vps instructions?

[swanson]

Resolves #146