infosecn1nja
/
metasploit-framework
mirror of https://github.com/infosecn1nja/metasploit-framework.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
metasploit-framework/config/database.yml.example

33 lines
1.1 KiB
Plaintext
Raw Permalink Normal View History

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 20:43:25 +00:00
# To set up a metasploit database, follow the directions hosted at:
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 16:05:03 +00:00
# http://r-7.co/MSF-DEV#set-up-postgresql
update database.yml.example to be something reasonable
2016-02-16 15:12:34 +00:00
#
# Kali Linux and the Omnibus installers both include an easy wrapper script for
# managing your database, which may be more convenient than rolling your own.
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 20:46:18 +00:00
development: &pgsql
adapter: postgresql
database: metasploit_framework_development
username: metasploit_framework_development
password: __________________________________
host: localhost
port: 5432
update database.yml.example to be something reasonable
2016-02-16 15:12:34 +00:00
pool: 200
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 20:46:18 +00:00
timeout: 5
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 20:43:25 +00:00
# You will often want to seperate your databases between dev
# mode and prod mode. Absent a production db, though, defaulting
# to dev is pretty sensible for many developer-users.
production: &production
<<: *pgsql
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 20:46:18 +00:00
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
#
# Note also, sqlite3 is totally unsupported by Metasploit now.
test:
<<: *pgsql
database: metasploit_framework_test
username: metasploit_framework_test
password: ___________________________