Commit Graph

4 Commits (7b29e6e0571cd76210d3611372ac1dd38dd5213f)

Author SHA1 Message Date
Brent Cook 1263a82d1e update database.yml.example to be something reasonable 2016-02-16 09:12:34 -06:00
Tod Beardsley 67065e104a
Update database.yml.example to ref MSF-DEV
We no longer rely on the Fedora Project's documentation for setting up a
PostgreSQL database. The comment doc here should reflect this change.
2015-06-16 11:05:03 -05:00
Tod Beardsley 881d16e701 Add some friendlier defaults to database.yml
Actually let people get going out of the gate without forcing them to
puzzle out database.yml configurations. Also gives some hints on how to
set up a database.

Today, if you merely copy and paste from database.yml.example, you'll
get yelled at:

````
$ ./msfconsole -L -y config/database.yml
[-] No database definition for environment production
````
2013-04-19 15:43:25 -05:00
Luke Imhoff 2604fad164 Allow use of rake db tasks
[#46224565]

The following rake tasks are added and work similar to how they work in
rails apps:
* db:create
* db:drop
* db:migrate
* db:migrate:status
* db:rollback
* db:schema:dump
* db:schema:load
* db:seed (but no db seeds defined at this time)
* db:setup
* db:version

The hidden task db:test:prepare is also available, which means `rake
spec` can depend on it so that the test database is dropped and
recreated from the development database when running specs (Although
there are yet to be database tests, this branch is in preparation for
that work that will be split between multiple developers.)
2013-03-14 15:46:18 -05:00