Files
www.gittip.com/default_local.env
Chad Whitacre ef014da733 Start using a db in the cloud for dev; #415
Rather than requiring a local Postgres instance in order to stand up
Gittip, this connects to a db in the cloud (a free plan from Heroku
Postgres). The plan is to reset this database in the cloud every six
hours or something, populated with fake data. That way people can get
started hacking on Gittip more easierly.

For running tests we should use postgression.com for ephemeral,
single-use databases.
2013-04-25 14:34:35 -04:00

19 lines
854 B
Bash

CANONICAL_HOST=
CANONICAL_SCHEME=http
DATABASE_URL=postgres://vprkgneaqxaqvu:jkaZ2shu3IBKGM0cHiXRnC8DJO@ec2-54-225-91-60.compute-1.amazonaws.com:5432/d14eguq4ovs8m
DATABASE_MAXCONN=10
STRIPE_SECRET_API_KEY=1
STRIPE_PUBLISHABLE_API_KEY=1
BALANCED_API_SECRET=90bb3648ca0a11e1a977026ba7e239a9
GITHUB_CLIENT_ID=3785a9ac30df99feeef5
GITHUB_CLIENT_SECRET=e69825fafa163a0b0b6d2424c107a49333d46985
GITHUB_CALLBACK=http://localhost:8537/on/github/associate
BITBUCKET_CONSUMER_KEY=b8yzpsurhsmJufUqzh
BITBUCKET_CONSUMER_SECRET=WF3q2g7naRHeeGUjnxyRwPLVhMBU4dmP
BITBUCKET_CALLBACK=http://localhost:8537/on/bitbucket/associate
TWITTER_CONSUMER_KEY=QBB9vEhxO4DFiieRF68zTA
TWITTER_CONSUMER_SECRET=mUymh1hVMiQdMQbduQFYRi79EYYVeOZGrhj27H59H78
TWITTER_CALLBACK=http://127.0.0.1:8537/on/twitter/associate
MIXPANEL_TOKEN=cb9dec68ac0ee57071f0be39f164a417
NANSWERS_THRESHOLD=2