Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

(#18228) updates README for style

This commit fixes style issues in the getting started README.
  • Loading branch information...
commit fd2e9904ede2d632598163f66073d130b23d7dbc 1 parent a313832
authored December 19, 2012

Showing 1 changed file with 21 additions and 20 deletions. Show diff stats Hide diff stats

  1. 41  README_GETTING_STARTED.md
41  README_GETTING_STARTED.md
Source Rendered
@@ -136,10 +136,11 @@ sufficient for many real-world deployments depending on the number of nodes
136 136
 you’re managing.  So, what would our manifest look like in this case?
137 137
 
138 138
     node puppetmaster {
139  
-       # Configure puppetdb and its underlying database
140  
-       include puppetdb
141  
-       # Configure the puppet master to use puppetdb
142  
-       include puppetdb::master::config
  139
+     # Configure puppetdb and its underlying database
  140
+     include puppetdb
  141
+
  142
+     # Configure the puppet master to use puppetdb
  143
+     include puppetdb::master::config
143 144
     }
144 145
 
145 146
 
@@ -179,30 +180,30 @@ scenario might look like:
179 180
 
180 181
     # This node is our Puppet master.
181 182
     node puppet {
182  
-        # Here we configure the puppet master to use PuppetDB,
183  
-        # and tell it that the hostname is ‘puppetdb’
184  
-        class { 'puppetdb::master::config':
185  
-            puppetdb_server => 'puppetdb',
186  
-        }
  183
+      # Here we configure the puppet master to use PuppetDB,
  184
+      # and tell it that the hostname is ‘puppetdb’
  185
+      class { 'puppetdb::master::config':
  186
+        puppetdb_server => 'puppetdb',
  187
+      }
187 188
     }
188 189
 
189 190
     # This node is our postgres server
190 191
     node puppetdb-postgres {
191  
-        # Here we install and configure postgres and the puppetdb
192  
-        # database instance, and tell postgres that it should
193  
-        # listen for connections to the hostname ‘puppetdb-postgres’
194  
-        class { 'puppetdb::database::postgresql':
195  
-            listen_addresses => 'puppetdb-postgres',
196  
-        }
  192
+      # Here we install and configure postgres and the puppetdb
  193
+      # database instance, and tell postgres that it should
  194
+      # listen for connections to the hostname ‘puppetdb-postgres’
  195
+      class { 'puppetdb::database::postgresql':
  196
+        listen_addresses => 'puppetdb-postgres',
  197
+      }
197 198
     }
198 199
 
199 200
     # This node is our main puppetdb server
200 201
     node puppetdb {
201  
-        # Here we install and configure PuppetDB, and tell it where to
202  
-        # find the postgres database.
203  
-        class { 'puppetdb::server':
204  
-            database_host      => 'puppetdb-postgres',
205  
-        }
  202
+      # Here we install and configure PuppetDB, and tell it where to
  203
+      # find the postgres database.
  204
+      class { 'puppetdb::server':
  205
+        database_host => 'puppetdb-postgres',
  206
+      }
206 207
     }
207 208
 
208 209
 That’s it!  This should be all it takes to get a 3-node, distributed

0 notes on commit fd2e990

Please sign in to comment.
Something went wrong with that request. Please try again.