Update MirrorProtocol fixture data

Move it to the correct location and add the new field. Also tidy up some of
the instructions dealing with loading this data.

Signed-off-by: Dan McGee <dan@archlinux.org>

README

@@ -44,19 +44,21 @@ will probably want the following:
 
 4. Sync the database to create it.
 
-        $ python manage.py syncdb
+        $ ./manage.py syncdb
 
 5. Migrate changes.
 
-        $ python manage.py migrate
+        $ ./manage.py migrate
 
 6. Load the fixtures to prepopulate some data.
 
-        $ python manage.py loaddata main/fixtures/arches.json main/fixtures/repos.json
+        $ ./manage.py loaddata main/fixtures/arches.json
+        # ./manage.py loaddata main/fixtures/repos.json
+        # ./manage.py loaddata mirrors/fixtures/mirrorprotocols.json
     
 7. Use the following commands to start a service instance
 
-        $ python manage.py runserver
+        $ ./manage.py runserver
 
 8. To optionally populate the database with real data:
 

main/fixtures/mirrorprotocols.json → mirrors/fixtures/mirrorprotocols.json

 [
     {
-        "pk": 2, 
-        "model": "main.mirrorprotocol", 
+        "pk": 1, 
+        "model": "mirrors.mirrorprotocol", 
         "fields": {
-            "protocol": "ftp"
+            "is_download": true, 
+            "protocol": "http"
         }
     }, 
     {
-        "pk": 1, 
-        "model": "main.mirrorprotocol", 
+        "pk": 2, 
+        "model": "mirrors.mirrorprotocol", 
         "fields": {
-            "protocol": "http"
+            "is_download": true, 
+            "protocol": "ftp"
         }
     }, 
     {
         "pk": 3, 
-        "model": "main.mirrorprotocol", 
+        "model": "mirrors.mirrorprotocol", 
         "fields": {
+            "is_download": false, 
             "protocol": "rsync"
         }
     }
-]
+]
\ No newline at end of file