[doc] also show command with sqlite since it's recommended
authorLaurent Peuch <cortex@worlddomination.be>
Tue, 26 Feb 2019 16:27:56 +0100
changeset 12411 ad0dbaf81c0c
parent 12410 7b32699cafc4
child 12412 519c80e23f75
[doc] also show command with sqlite since it's recommended
doc/tutorials/advanced/part04_ui-base.rst
--- a/doc/tutorials/advanced/part04_ui-base.rst	Tue Feb 26 16:26:33 2019 +0100
+++ b/doc/tutorials/advanced/part04_ui-base.rst	Tue Feb 26 16:27:56 2019 +0100
@@ -337,7 +337,7 @@
 
    In the 'cubicweb-ctl i18ncube' command, `sytweb` refers to the **cube**, while
    in the two other, it refers to the **instance** (if you can't see the
-   difference, reread CubicWeb's concept chapter !).
+   difference, reread `CubicWeb's concept chapter <../../intro/concepts/>`_!).
 
 
 Once I've checked it's ok, I simply have to bump the version number in the
@@ -348,7 +348,10 @@
 To generate a dump from the production site: ::
 
   $ cubicweb-ctl db-dump sytweb_instance
+  # if it's postgresql
   pg_dump -Fc --username=syt --no-owner --file /home/syt/etc/cubicweb.d/sytweb/backup/tmpYIN0YI/system sytweb
+  # if it's sqlite
+  gzip -c /home/psycojoker/etc/cubicweb.d/sytweb_instance/sytweb_instance.sqlite
   -> 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