1 | # Note: This FAQ is out-of-date for Bedrock 0.3+.
|
2 |
|
3 | # Development
|
4 |
|
5 | ## How do I setup a local bedrock development environment?
|
6 |
|
7 | See the [CONTRIBUTING][] documentation for full details.
|
8 |
|
9 | ## What should my mongo database config look like?
|
10 |
|
11 | If you choose to use the MongoDB module, a simple config like the following
|
12 | is fine:
|
13 |
|
14 | dbpath=/var/lib/mongodb
|
15 | logpath=/var/log/mongodb/mongodb.log
|
16 | logappend=true
|
17 | journal=true
|
18 | auth = true
|
19 |
|
20 | ## I'm getting an 'auth fails' Mongo error on startup. What's wrong?
|
21 |
|
22 | If you are using the MongoDB module, when the system first starts up it will
|
23 | connect to MongoDB as an administrator and create all of the necessary
|
24 | databases for Bedrock. If you get an 'auth fails' message, the most likely
|
25 | culprit is that the admin username and password you're using is wrong, or
|
26 | you forgot to setup a database admin.
|
27 |
|
28 | Check to make sure that the admin username and password is correct by logging
|
29 | into MongoDB manually:
|
30 |
|
31 | > mongo
|
32 | > use admin
|
33 | > db.auth('admin', 'password')
|
34 |
|
35 | The command above assumes that 'admin' is the username and 'password' is your
|
36 | password. If it's not, put in whatever your admin username and password is
|
37 | at the time. The three commands above should return 1 (success). If the
|
38 | return value is 0, then your admin user isn't configured correctly. Refer to
|
39 | [CONTRIBUTING][] to learn how to configure the MongoDB administrator.
|
40 |
|
41 | ## How do I clear all Bedrock data from the MongoDB database?
|
42 |
|
43 | Make sure that the Bedrock process has been halted, then drop the master
|
44 | Bedrock database and the local Bedrock database collection:
|
45 |
|
46 | > mongo
|
47 | > use admin
|
48 | > db.auth('admin', 'password')
|
49 | > use bedrock_dev
|
50 | > db.dropDatabase()
|
51 | > use local
|
52 | > db.bedrock_dev.drop()
|
53 | > exit
|
54 |
|
55 | # Licensing
|
56 |
|
57 | ## Is Bedrock Open Source?
|
58 |
|
59 | No. It does not fit any of the OSI-approved definitions for
|
60 | "Open Source Software" primarily because we restrict its
|
61 | use to non-commercial use. Commercial use requires a license.
|
62 |
|
63 | You can look at and contribute to the source. You can use it
|
64 | for non-commercial projects. The next question in the FAQ
|
65 | explains why we have decided to release Bedrock under this
|
66 | model.
|
67 |
|
68 | ## Why isn't this released under an open source license?
|
69 |
|
70 | Our company loves open source. We release many of our projects under
|
71 | GPLv2, AGPLv3, MIT, BSD, and Creative Commons licenses. We
|
72 | contribute heavily to the open source world and benefit greatly from
|
73 | open source software.
|
74 |
|
75 | There are a number of reasons that this particular product isn't
|
76 | open source:
|
77 |
|
78 | * We need to feed our families and this product generates revenue for us.
|
79 | * We need to fund development of our core company products and
|
80 | we currently believe that releasing this product as open source
|
81 | will not enable us to do that.
|
82 | * We have tried the "pay for support" open source model and it has not
|
83 | worked very well for our company. Very large companies, far bigger
|
84 | than ours, regularly benefit from our work and provide nothing in
|
85 | return.
|
86 |
|
87 | We wish this were not true. We wish we could just develop great
|
88 | technology, release it to the world, and people would pay us for it.
|
89 | To date, the revenue we've received from other large companies that have
|
90 | benefitted from projects we've open sourced wouldn't even cover a month
|
91 | of operations. The reality is that large companies don't pay small
|
92 | companies for their work unless they absolutely have to.
|
93 |
|
94 | That said, we do also want to be a good citizen of the Web. We want to
|
95 | help students, researchers, hobbyists, and non-commercial enterprises
|
96 | use our software for research and the greater good. That is why we have
|
97 | decided to try a middle path - a non-commercial license for the software.
|
98 | This approach ensures that we help those that can't afford a commercial
|
99 | license while not putting ourselves out of business.
|
100 |
|
101 | In the future, we hope to include contributors to the project in a split
|
102 | of the revenue. We are still working out the details on how to do that
|
103 | fairly, but that's the direction we're headed. We want this software to
|
104 | put food on the table for not just us, but all contributors to the project
|
105 | as well.
|
106 |
|
107 | ## I work for a startup, is Bedrock expensive to license?
|
108 |
|
109 | No, it's quite affordable for a startup and we're very careful to not
|
110 | endanger the startup with ill-timed license fee schedules. We work
|
111 | with startups on a regular basis and we want them to succeed because
|
112 | we want them to become customers.
|
113 |
|
114 | ## I work for a major corporation, is Bedrock expensive to license?
|
115 |
|
116 | Bedrock easily provides a 10x return on investment for a large company.
|
117 | It took years to write and refine it, which is money that your organization
|
118 | does not have to spend making the same mistakes that we did.
|
119 |
|
120 | [AUTHORS]: AUTHORS.md
|
121 | [FEATURES]: FEATURES.md
|
122 | [CONTRIBUTING]: CONTRIBUTING.md
|
123 | [FAQ]: FAQ.md
|
124 | [LICENSE]: LICENSE.md
|