Skip to content

Commit

Permalink
Fixed a few typos in mongodb/README.md and moved build/ directory
Browse files Browse the repository at this point in the history
to the root-level of the cookbook repository.
  • Loading branch information
Markus Korn committed Sep 5, 2011
1 parent dbf6ed0 commit 1aaeaa0
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

DIRS = mongodb

BUILD_DIR=../build
BUILD_DIR=build

dist: clean
mkdir -p $(BUILD_DIR)
Expand Down
2 changes: 1 addition & 1 deletion mongodb/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
COOKBOOK=mongodb
BRANCH=master

BUILD_DIR=../../build
BUILD_DIR=../build
DIST=$(BUILD_DIR)/$(COOKBOOK).tar.gz

all: metadata.json
Expand Down
8 changes: 4 additions & 4 deletions mongodb/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Installs and configures various kind of MongoDB setups, including sharding and r

## Platform:

The cookbook aims to be platform independant, but is best tested on debian squeze systems.
The cookbook aims to be platform independant, but is best tested on debian squeeze systems.

# DEFINITIONS:

Expand Down Expand Up @@ -65,10 +65,10 @@ The result is a new system service with

If you would like to add your mongodb instance to a replicaset all you have to
do is adding `mongodb::replicaset` to the node's run_list and make sure to add
one ore more roles with the same prefix to all members of the replicaset. This
one or more roles with the same prefix to all members of the replicaset. This
prefix has to be defined in `mongodb[:cluster_role_prefix]` . For example you
could create a role called "my_replicaset" and add this role to the run_list of
all nodes which should be in the replicaset. finally you only have to define
all nodes which should be in the replicaset. Finally you only have to define
`mongodb[:cluster_role_prefix]` for all nodes in this cluster. This way they are
able to find each other.

Expand Down Expand Up @@ -108,7 +108,7 @@ prefix, and define this prefix, to identify all members. Also shard names are
important to distinguish the different shards.

This is esp. important when you want to replicate shards. The setup is not much
different to the one described above. all you have to do is adding the
different to the one described above. All you have to do is adding the
`mongodb::replicaset` recipe to all shard nodes, and make sure that all shard
nodes which should be in the same replicaset have the same shard name.

Expand Down

0 comments on commit 1aaeaa0

Please sign in to comment.