[doc] fix, the cube name was used, it was the instance named that was needed
authorLaurent Peuch <cortex@worlddomination.be>
Tue, 26 Feb 2019 16:26:33 +0100
changeset 12410 7b32699cafc4
parent 12409 326949ee87cb
child 12411 ad0dbaf81c0c
[doc] fix, the cube name was used, it was the instance named that was needed
doc/tutorials/advanced/part04_ui-base.rst
--- a/doc/tutorials/advanced/part04_ui-base.rst	Tue Feb 26 16:25:59 2019 +0100
+++ b/doc/tutorials/advanced/part04_ui-base.rst	Tue Feb 26 16:26:33 2019 +0100
@@ -347,15 +347,15 @@
 
 To generate a dump from the production site: ::
 
-  $ cubicweb-ctl db-dump sytweb
+  $ cubicweb-ctl db-dump sytweb_instance
   pg_dump -Fc --username=syt --no-owner --file /home/syt/etc/cubicweb.d/sytweb/backup/tmpYIN0YI/system sytweb
   -> backup file /home/syt/etc/cubicweb.d/sytweb/backup/sytweb-2010-07-13_10-22-40.tar.gz
 
 I can now get back the dump file (:file:`sytweb-2010-07-13_10-22-40.tar.gz`) to my test
 machine (using `scp` for instance) to restore it and start migration: ::
 
-  $ cubicweb-ctl db-restore sytweb sytweb-2010-07-13_10-22-40.tar.gz
-  $ cubicweb-ctl upgrade sytweb
+  $ cubicweb-ctl db-restore sytweb_instance /path/path/to/sytweb-2010-07-13_10-22-40.tar.gz
+  $ cubicweb-ctl upgrade sytweb_instance
 
 You'll have to answer some questions, as we've seen in `an earlier post`_.