Move the deployment section from README.development to the man page.

[dead/htsn-import.git] / doc / README.development

diff --git a/doc/README.development b/doc/README.development
index b1df69861650a579959fa32b576590d00e978627..e58b418edf67adc2f755e98cff7e9586f87b97c6 100644 (file)
--- a/doc/README.development
+++ b/doc/README.development
@@ -27,23 +27,3 @@ If there's an error, you'll see something like the following:
   contents:   <Title>IRL - Firestone 600 - Final Results</Title><Track_Location>
   Texas Motor Sp...
   []
-
-
-== Creating the Database Schema (Deployment) ==
-
-When deploying for the first time, the target database will most
-likely be empty. The schema will be migrated when a new document type
-is seen, but this has a downside: it can be months before every
-supported document type has been seen once. This can make it difficult
-to test the database permissions.
-
-Since all of the test XML documents have old timestamps, one easy
-workaround is the following: simply import all of the test XML
-documents, and then delete them. This will force the migration of the
-schema, after which you can set and test the database permissions.
-
-Something as simple as,
-
-  $ find ./test/xml -iname '*.xml' | xargs htsn-import -c foo.sqlite
-
-should do it.