41 located in :file:`~/etc/cubicweb.d/myinstance/*`. To launch it, you |
41 located in :file:`~/etc/cubicweb.d/myinstance/*`. To launch it, you |
42 just type :: |
42 just type :: |
43 |
43 |
44 cubicweb-ctl start -D myinstance |
44 cubicweb-ctl start -D myinstance |
45 |
45 |
46 The option `-D` specify the *debug mode* : the instance is not running in |
46 The option `-D` specifies the *debug mode* : the instance is not |
47 server mode and does not disconnect from the termnial, which simplifies debugging |
47 running in server mode and does not disconnect from the terminal, |
48 in case the instance is not properly launched. You can see how it looks by |
48 which simplifies debugging in case the instance is not properly |
49 visiting the URL `http://localhost:8080` (the port number depends of your |
49 launched. You can see how it looks by visiting the URL |
50 configuration). To login, please use the cubicweb administrator login/psswd you |
50 `http://localhost:8080` (the port number depends of your |
51 defined when you created the instance. |
51 configuration). To login, please use the cubicweb administrator |
|
52 login/psswd you defined when you created the instance. |
52 |
53 |
53 To shutdown the instance, Crtl-C in the terminal window is enough. |
54 To shutdown the instance, Crtl-C in the terminal window is enough. |
54 If you did not use the option `-D`, then type :: |
55 If you did not use the option `-D`, then type :: |
55 |
56 |
56 cubicweb-ctl stop myinstance |
57 cubicweb-ctl stop myinstance |
69 |
70 |
70 The command is:: |
71 The command is:: |
71 |
72 |
72 cubicweb-ctl upgrade myinstance |
73 cubicweb-ctl upgrade myinstance |
73 |
74 |
74 XXX write me |
75 A series of questions will be asked. It always starts with a proposal |
|
76 to make a backup of your sources (where it applies). Unless you know |
|
77 exactly what you are doing (i.e. typically fiddling in debug mode, but |
|
78 definitely NOT migrating a production instance), you should answer YES |
|
79 to that. |
75 |
80 |
|
81 The remaining questions concern the migration steps of |cubicweb|, |
|
82 then of the cubes that form the whole application, in reverse |
|
83 dependency order. |
|
84 |
|
85 In principle, if the migration scripts have been properly written and |
|
86 tested, you should answer YES to all questions. |
|
87 |
|
88 Somtimes, typically while debugging a migration script, something goes |
|
89 wrong and the migration fails. Unfortunately the databse may be in an |
|
90 incoherent state. You have two options here: |
|
91 |
|
92 * fix the bug, restore the database and restart the migration process |
|
93 from scratch (quite recommended in a production environement) |
|
94 |
|
95 * try to replay the migration up to the last successful commit, that |
|
96 is answering NO to all question up to the step that failed, and |
|
97 finish by answering YES to the remaining questions. |
|
98 |