<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -26,30 +26,31 @@ Setting up a build slave
    See the documentation for `the build slave recipe`_ for more
    info on the build slave options.
    
-3. Give the slave a good, unique name that'll tell what it is and what it does
-   (i.e. ``osx-10.5-python2.5-sqlite``, ``ubuntu-hardy-python2.6-mysql-5.0``,
-   etc.)
+3. Give the slave a good, unique name that'll tell what it is and what it
+   does (i.e. ``osx-10.5-python2.5-sqlite``,
+   ``ubuntu-hardy-python2.6-mysql-5.0``, etc.)
 
 4. Make up a slave password.
    
 5. Make sure the slave environment has ``DJANGO_SETTINGS_MODULE`` and
-   ``PYTHONPATH`` set correctly, and make sure that ``DJANGO_SETTINGS_MODULE``
-   exists and is configured correctly.
-   
-   Note that the same slave may test multiple branches, so you'll need to make
-   sure that nothing's shared between the slaves. See
-   ``testsettings/postgres.py`` for one of the things you'll need to do: set
-   ``TEST_DATABASE_NAME`` to something that'll be different for each slave.
+   ``PYTHONPATH`` set correctly, and make sure that
+   ``DJANGO_SETTINGS_MODULE`` exists and is configured correctly.
 
+    Note that the same slave may test multiple branches, so you'll need to
+    make sure that nothing's shared between the slaves. See
+    ``testsettings/postgres.py`` for one of the things you'll need to do:
+    set ``TEST_DATABASE_NAME`` to something that'll be different for each
+    slave.
 
-6. Create the buildbot by running ``./bin/buildout`` from the slave directory.
+6. Create the buildbot by running ``./bin/buildout`` from the slave
+   directory.
 
 7. Start the slave: ``./bin/&lt;my-slave-name&gt; start``
 
-8. Send the buildbot name and password to *jacob -at- jacobian -dot- org* to get
-   added to the master.
+8. Send the buildbot name and password to *jacob -at- jacobian -dot- org*
+   to get added to the master.
    
-9. Watch your buildbot: if it starts failing because of problems on the server
-   it'll get de-listed.
+9. Watch your buildbot: if it starts failing because of problems on the
+   server it'll get de-listed.
 
 .. _the build slave recipe: http://pypi.python.org/pypi/collective.buildbot/0.3.3#the-build-slave-recipe</diff>
      <filename>README.rst</filename>
    </modified>
    <modified>
      <diff>@@ -10,4 +10,5 @@ DATABASE_USER = 'jacob'
 
 # Make sure we get a distinct test database name -- this
 # settings file might be used to run multiple tests.
-TEST_DATABASE_NAME = &quot;djangotests_%s&quot; % (os.getpid())
\ No newline at end of file
+TEST_DATABASE_NAME = &quot;djangotests_%s&quot; % (os.getpid())
+TEST_DATABASE_CHARSET = 'UTF8'
\ No newline at end of file</diff>
      <filename>slave/testsettings/postgres.py</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>d9a54c6817c42855284d481b53333103a4c431c4</id>
    </parent>
  </parents>
  <author>
    <name>Jacob Kaplan-Moss</name>
    <email>jacob@jacobian.org</email>
  </author>
  <url>http://github.com/jacobian/django-buildbots/commit/2dd4ffc97372b19556a7c8be62699891536281b8</url>
  <id>2dd4ffc97372b19556a7c8be62699891536281b8</id>
  <committed-date>2009-04-18T12:20:34-07:00</committed-date>
  <authored-date>2009-04-18T12:20:34-07:00</authored-date>
  <message>Updated README, and added a missing TEST_DATABASE_CHARSET to example settings.</message>
  <tree>ae3dd8e22867047e8611e23a03eb6c6efc1c9e2e</tree>
  <committer>
    <name>Jacob Kaplan-Moss</name>
    <email>jacob@jacobian.org</email>
  </committer>
</commit>
