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
````
Note that this commit needed a --no-verify because of the erroneous
check in msftidy for writing to stdout. The particular syntax of this
payload makes it look like we're doing that when we're really not.
So don't sweat it.
This was landed by @todb-r7 on #1709 but that was premature. #1717 was
a proposed set of fixes, but it didn't go far enough.
@jhart-r7 and @jvazquez-r7 should revisit this module for sure, there's
some good stuff in there, but it's not ready for a real release quite
yet. Take a look at the issues discussed in those PRs and open a new PR
with a new module?
Sorry for the switcheroo, not trying to be a jerk.
[Closes#1717]
Some users are having trouble installing pcap. Others want postgres to
remain optional. The move to requiring bundler in a git environment has
made this hard.
This commit provides a path for these users. By default, bundler will
install all gems, including postgres and pcaprub. If it fails to
install some, Metasploit will not function. But there is hope. Users
can explicitly exclude the gem groups they don't want.
For example:
bundle install --without db pcap
will exclude the pcap and postgres gems (and their depedencies).
bundle install --without db pcap development test
will exclude all non-essential gems.
The good news is that the user only needs to use the `--without` option
once. Bundler will remember it. So future runs can still do `bundle
install` (or simply `bundle`) and the gems will still be excluded. And
if the user changes their mind and wants the optional gems, they can
remove their stored *without* preference using:
bundle config --delete without
[FIXRM #7891]