Browse Source

Fix coverage2sql-db-manage usage document

This commit fixes coverage2sql-db-manage usage in README.rst. We can't
use use --database-connection option now. So this commit just removes
the description. We may add the option in the future, though.

Change-Id: I6018fc5cf394c99ccf5f57bb33f30a21eab7456b
Masayuki Igawa 2 years ago
parent
commit
89186aa5d5
No account linked to committer's email address
1 changed files with 3 additions and 7 deletions
  1. 3
    7
      README.rst

+ 3
- 7
README.rst View File

@@ -30,15 +30,11 @@ DB Setup
30 30
 
31 31
 The usage of coverage2sql is split into 2 stages. First you need to prepare a
32 32
 database with the proper schema; coverage2sql-db-manage should be used to do
33
-this. The utility requires db connection info which can be specified on the
34
-command or with a config file. Obviously the sql connector type, user,
33
+this. The utility requires db connection info which can be specified with a
34
+config file. Obviously the sql connector type, user,
35 35
 password, address, and database name should be specific to your environment.
36 36
 coverage2sql-db-manage will use alembic to setup the db schema. You can run the
37
-db migrations with the command::
38
-
39
-    coverage2sql-db-manage --database-connection mysql://coverage:pass@127.0.0.1/coverage upgrade head
40
-
41
-or with a config file::
37
+db migrations with a config file::
42 38
 
43 39
     coverage2sql-db-manage --config-file etc/coverage2sql.conf upgrade head
44 40
 

Loading…
Cancel
Save