Merge branch 'master' of git.20c.com:pdb/gh-peeringdb

docs/deploy.md

@@ -9,16 +9,6 @@ This document uses the following variables
 export PDB_REPO=git@github.com:peeringdb/peeringdb.git
 ```
 
-### Install obfuscation tools (Only needed if you want to obfuscate js)
-
-```sh
-git clone src.20c.com:20c/sys-deploy
-mkdir -p ~/.local/google
-wget https://dl.google.com/closure-compiler/compiler-latest.zip
-unzip compiler-latest.zip
-mv compiler.jar ~/.local/google
-```
-
 ### Install facsimile
 
 ```sh
@@ -109,6 +99,45 @@ mysql -u root -p < .facsimile/tmp/RELEASE/dev/peeringdb/init.sql
 ./manage.py runserver
 ```
 
+## Populating with data
+
+There are currently 2 ways to get some data into your developer instance
+
+1) Sync from production peeringdb - slow, but accurate data
+2) Generate test data - fast, but marginally useful test data
+
+### 1) Sync from Production
+
+You can populate your data from peeringdb.com using
+
+```sh
+./manage.py pdb_load_data
+```
+
+However be prepared for this to take 15-20 minutes as it will not only sync the entities, but also set up usergroups for each organization and so forth.
+
+This can only be used to populate initial data. Once you have started adding / updating objects and your data diverges from production data, it is no longer useful to call this command nor will it allow you to.
+
+Special Note: this will only sync data visible to everyone, any fields or rows hidden behind authentication will be missed.
+
+### 2) Generate test data
+
+Alternatively a faster way to get data into your instance is to generate a set of test data.
+
+The data generated has no relation to real world data, but should be good enough for testing purposes
+
+```sh
+./manage.py pdb_generate_test_data --commit
+```
+
+## Admin
+
+The admin area can be accessed from the `/cp` endpoint, you will need to have a superuser to access it
+
+```sh
+./manage.py createsuperuser
+```
+
 ## Hangups
 
 ### Authentication not working