65 `postgres-contrib-8.3` and `postgresql-plpython-8.3`. |
65 `postgres-contrib-8.3` and `postgresql-plpython-8.3`. |
66 |
66 |
67 |
67 |
68 Then you can install: |
68 Then you can install: |
69 |
69 |
70 * `pyro` if you wish the repository is accessible through Pyro |
70 * `pyro` if you wish the repository to be accessible through Pyro |
71 or if the client and the server are not running on the same machine |
71 or if the client and the server are not running on the same machine |
72 (in suche case the packages will have to be isntalled on both |
72 (in which case the packages will have to be installed on both |
73 machines) |
73 machines) |
74 |
74 |
75 * `python-ldap` if you plan to use a LDAP source on the server |
75 * `python-ldap` if you plan to use a LDAP source on the server |
76 |
76 |
77 .. _ConfigurationEnv: |
77 .. _ConfigurationEnv: |
78 |
78 |
79 Environment configuration |
79 Environment configuration |
80 ------------------------- |
80 ------------------------- |
81 |
81 |
82 If you installed `CubicWeb` by cloning the Mercurial forest, then you |
82 If you installed `CubicWeb` by cloning the Mercurial forest, then you |
83 will need to update the environment variable PYTHONPATH to add to it |
83 will need to update the environment variable PYTHONPATH by adding |
84 the path to the forest ``cubicweb``. |
84 the path to the forest ``cubicweb``: |
85 |
85 |
86 Add the following lines to either `.bashrc` or `.bash_profile` to configure |
86 Add the following lines to either `.bashrc` or `.bash_profile` to configure |
87 your development environment :: |
87 your development environment :: |
88 |
88 |
89 export PYTHONPATH=/full/path/to/cubicweb-forest |
89 export PYTHONPATH=/full/path/to/cubicweb-forest |
115 |
115 |
116 * Create a superuser for `CubicWeb` instance (**root**) :: |
116 * Create a superuser for `CubicWeb` instance (**root**) :: |
117 |
117 |
118 createuser -s username |
118 createuser -s username |
119 |
119 |
120 Initialize the password of the superuser you juste created with |
120 Initialize the password of the superuser you just created with |
121 ``su - postgres`` and ``psql``. |
121 ``su - postgres`` and ``psql``. |
122 |
122 |
123 This password will be asked to you later on where you will create an |
123 This password will be asked to you later on where you will create an |
124 instance with `cubicweb-ctl create` |
124 instance with `cubicweb-ctl create` |
125 |
125 |
126 [XXX] |
126 .. [XXX] Est-ce que ces etapes sont vraiment necessaires? sand : lors de l'installation de ma bdd cela n'a pas ete fait et il semble que tout aille bien. Doit etre verifie avec les experts. |
127 Est-ce que ces etapes sont vraiment necessaires? |
|
128 sand : lors de l'installation de ma bdd cela n'a pas ete fait |
|
129 et il semble que tout aille bien. Doit etre verifie avec les experts. |
|
130 |
127 |
131 * installation of plain-text index extension :: |
128 * installation of plain-text index extension :: |
132 |
129 |
133 cat /usr/share/postgresql/8.3/contrib/tsearch2.sql | psql -U username template1 |
130 cat /usr/share/postgresql/8.3/contrib/tsearch2.sql | psql -U username template1 |
134 |
131 |
138 |
135 |
139 |
136 |
140 Pyro configuration |
137 Pyro configuration |
141 ------------------ |
138 ------------------ |
142 |
139 |
143 If you use Pyro, it is required to have a name server Pyro runing on your |
140 If you use Pyro, it is required to have a name server Pyro running on your |
144 network (by default it is identified by a broadcast request). |
141 network (by default it is identified by a broadcast request). |
145 |
142 |
146 To do so, you need to : |
143 To do so, you need to : |
147 |
144 |
148 * launch the server manually before starting cubicweb with `pyro-ns` |
145 * launch the server manually before starting cubicweb with `pyro-ns` |
149 |
146 |
150 * launch the server manually before starting cubicweb as a server with |
147 * launch the server manually before starting cubicweb as a server with |
151 `pyro-nsd start` |
148 `pyro-nsd start` |
152 |
149 |
153 * edit the file ``/etc/default/pyro-nsd`` so that the name server pyro |
150 * edit the file ``/etc/default/pyro-nsd`` so that the name server pyro |
154 will be launched automatically when the macine fire up |
151 will be launched automatically when the machine fire up |
155 |
152 |
156 |
153 |