335 |
335 |
336 .. Note:: |
336 .. Note:: |
337 |
337 |
338 In the 'cubicweb-ctl i18ncube' command, `sytweb` refers to the **cube**, while |
338 In the 'cubicweb-ctl i18ncube' command, `sytweb` refers to the **cube**, while |
339 in the two other, it refers to the **instance** (if you can't see the |
339 in the two other, it refers to the **instance** (if you can't see the |
340 difference, reread CubicWeb's concept chapter !). |
340 difference, reread `CubicWeb's concept chapter <../../intro/concepts/>`_!). |
341 |
341 |
342 |
342 |
343 Once I've checked it's ok, I simply have to bump the version number in the |
343 Once I've checked it's ok, I simply have to bump the version number in the |
344 :file:`__pkginfo__` module to trigger a migration once I'll have updated the code on |
344 :file:`__pkginfo__` module to trigger a migration once I'll have updated the code on |
345 the production site. I can check then check the migration is also going fine, by |
345 the production site. I can check then check the migration is also going fine, by |
346 first restoring a dump from the production site, then upgrading my test instance. |
346 first restoring a dump from the production site, then upgrading my test instance. |
347 |
347 |
348 To generate a dump from the production site: :: |
348 To generate a dump from the production site: :: |
349 |
349 |
350 $ cubicweb-ctl db-dump sytweb_instance |
350 $ cubicweb-ctl db-dump sytweb_instance |
|
351 # if it's postgresql |
351 pg_dump -Fc --username=syt --no-owner --file /home/syt/etc/cubicweb.d/sytweb/backup/tmpYIN0YI/system sytweb |
352 pg_dump -Fc --username=syt --no-owner --file /home/syt/etc/cubicweb.d/sytweb/backup/tmpYIN0YI/system sytweb |
|
353 # if it's sqlite |
|
354 gzip -c /home/psycojoker/etc/cubicweb.d/sytweb_instance/sytweb_instance.sqlite |
352 -> backup file /home/syt/etc/cubicweb.d/sytweb/backup/sytweb-2010-07-13_10-22-40.tar.gz |
355 -> backup file /home/syt/etc/cubicweb.d/sytweb/backup/sytweb-2010-07-13_10-22-40.tar.gz |
353 |
356 |
354 I can now get back the dump file (:file:`sytweb-2010-07-13_10-22-40.tar.gz`) to my test |
357 I can now get back the dump file (:file:`sytweb-2010-07-13_10-22-40.tar.gz`) to my test |
355 machine (using `scp` for instance) to restore it and start migration: :: |
358 machine (using `scp` for instance) to restore it and start migration: :: |
356 |
359 |