Changeset 696
- Timestamp:
- Jun 30, 2015, 10:35:39 AM (9 years ago)
- Location:
- branches/PublicaMundi_David-devel/docs
- Files:
-
- 3 added
- 1 deleted
- 38 edited
- 5 moved
Legend:
- Unmodified
- Added
- Removed
-
branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/breadcrumbs.html
r689 r696 8 8 <li>{{ title }}</li> 9 9 <li class="wy-breadcrumbs-aside"> 10 $ date$10 $Date$ 11 11 </li> 12 12 </ul> -
branches/PublicaMundi_David-devel/docs/_themes/sphinx_rtd_theme/layout.html
r659 r696 107 107 <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation"> 108 108 {% block menu %} 109 {% set toctree = toctree(maxdepth=2, collapse=False, includehidden= True) %}109 {% set toctree = toctree(maxdepth=2, collapse=False, includehidden=False) %} 110 110 {% if toctree %} 111 111 {{ toctree }} -
branches/PublicaMundi_David-devel/docs/api/classes.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/description.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/examples.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/howto.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/index.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/what.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/zoo-format-wps.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/zoo-process.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/zoo-request.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/api/zoo.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/client/example.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/client/howto.rst
- Property svn:keywords set to Date Author
r659 r696 39 39 40 40 Compiling ZOO-Client templates 41 --------------------------- 41 ---------------------------=== 42 42 43 In order to work with ZOO-Client, you will first need to compile the provided `Mustache <http://mustache.github.io/>`_ 44 templates using `Node.js <http://nodejs.org/>`__. The ZOO-Client templates are located in the ``/zoo-project/zoo-client/lib/tpl`` directory downloaded from svn. 43 In order to work with ZOO-Client, you will first need to compile the 44 provided `Mustache <http://mustache.github.io/>`_ templates using 45 `Node.js <http://nodejs.org/>`__. The ZOO-Client templates are located 46 in the ``/zoo-project/zoo-client/lib/tpl`` directory downloaded from 47 svn. 45 48 46 49 * Install Node.js (see related `documentation <https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager>`__.) … … 64 67 65 68 Building ZOO-Client documentation 66 -------------------------- 69 --------------------------------- 67 70 68 71 You may also build the ZOO-Client API documentation using `jsDoc -
branches/PublicaMundi_David-devel/docs/client/index.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/client/what.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/contribute/code.rst
- Property svn:keywords set to Date Author
r679 r696 13 13 14 14 Submit new code 15 --------------- -----------15 --------------- 16 16 17 17 For new comers 18 ************** ***********18 ************** 19 19 20 20 New source code or existing source code corrections (patches) should 21 be submitted using the ZOO-Project bug tracking system (`ZOO-Trac <http://zoo-project.org/trac>`__ ). 21 be submitted using the ZOO-Project bug tracking system (`ZOO-Trac 22 <http://zoo-project.org/trac>`__ ). 22 23 23 Create a new ticket in order to describe your code or patch and attach 24 it to the ticket (attach all the needed files needed to use your code 25 or patch). It will then be checked and discussed with the developers, 26 and can potentially be integrated and merged with the trunk. 24 Create a `new ticket <http://zoo-project.org/trac/newticket>`__ in 25 order to describe your code or patch and attach it to the ticket 26 (attach all the files required to use your code or patch). It will 27 then be checked and discussed with the developers, and can potentially 28 be integrated and merged with the trunk. 27 29 28 30 For registered developers -
branches/PublicaMundi_David-devel/docs/contribute/contributors.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/contribute/dev.rst
- Property svn:keywords set to Date Author
r665 r696 9 9 ----------------------------- 10 10 11 Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted. 11 Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted. 12 12 13 13 Removal of SVN commit access should be handled by the same process. … … 24 24 ------------------ 25 25 26 A list of all project committers will be kept in the main zoo-project directory (called COMMITTERS) listing for each SVN committer:26 A list of all project committers will be kept in the main zoo-project directory (called `COMMITTERS <http://zoo-project.org/trac/browser/trunk/zoo-project/COMMITTERS>`__) listing for each SVN committer: 27 27 28 28 * Userid: the id that will appear in the SVN logs for this person. 29 29 * Full name: the users actual name. 30 30 * Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest. 31 31 32 32 33 SVN Administrator -
branches/PublicaMundi_David-devel/docs/contribute/doc.rst
- Property svn:keywords set to Date Author
r665 r696 28 28 ........................................ 29 29 30 The current structure of the ZOO Project documentation process is for developers with :ref:`SVN <svn>` commit access to maintain their documents in reStructuredText format, and therefore all documents live in the /docs directory in SVN. The `Sphinx <http://sphinx.pocoo.org/>`__ documentation generator is used to convert the reStructuredText files to html, and the live 31 website is then updated on an hourly basis. 30 The current structure of the ZOO Project documentation process is for 31 developers with :ref:`SVN <svn>` commit access to maintain their 32 documents in reStructuredText format, and therefore all documents live 33 in the /docs directory in SVN. The `Sphinx 34 <http://sphinx.pocoo.org/>`__ documentation generator is used to 35 convert the reStructuredText files to html, and the live website is 36 then updated on an hourly basis. 32 37 33 38 … … 49 54 :: 50 55 51 sudo easy_install Sphinx 56 sudo easy_install Sphinx==1.3.1 52 57 53 58 .. note:: 54 59 55 Make sure you install Sphinx 1. 0 or more recent. See note above.60 Make sure you install Sphinx 1.3.1 or more recent. 56 61 57 62 * Checkout the /docs directory from SVN, such as: … … 88 93 :: 89 94 90 sudo easy_install Sphinx95 sudo easy_install-2.7 Sphinx==1.3.1 91 96 92 97 .. note:: 93 98 94 Make sure you install Sphinx 1. 0 or more recent. See note above.99 Make sure you install Sphinx 1.3.1 or more recent. 95 100 96 101 * Install `MacTex <http://www.tug.org/mactex/2009/>`__ if you want to build pdfs … … 127 132 :: 128 133 129 easy_install Sphinx 134 easy_install Sphinx==1.3.1 130 135 131 136 ...you should see message: "Finished processing dependencies for Sphinx" … … 133 138 .. note:: 134 139 135 Make sure you install Sphinx 1. 0or more recent. See note above.140 Make sure you install Sphinx 1.3.1 or more recent. See note above. 136 141 137 142 * Install `MiKTeX <http://miktex.org>`__ if you want to build pdfs -
branches/PublicaMundi_David-devel/docs/contribute/howto.rst
- Property svn:keywords set to Date Author
r663 r696 1 1 How to contribute ? 2 ================== 2 =================== 3 3 4 4 Please consider the following simple rules if you would like to contribute to the `ZOO-Project <http://zoo-project.org>`__ open source software. … … 37 37 .. csv-table:: 38 38 39 Name,Description ,Address40 zoo-discuss,General mailing list for ZOO-Project users and developers,zoo-discuss@lists.osgeo.org41 zoo-psc,Project Steering Committe mailing list,zoo-psc@lists.osgeo.org39 Name,Description 40 `zoo-discuss <http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss>`__,General mailing list for ZOO-Project users and developers 41 `zoo-psc <http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc>`__,Project Steering Committe mailing list 42 42 43 43 -
branches/PublicaMundi_David-devel/docs/contribute/index.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/contribute/translate.rst
- Property svn:keywords set to Date Author
r679 r696 23 23 for i in Title Abstract; 24 24 do 25 grep $i $j | sed "s:$i = :_ (\":g;s:$:\"):g" ;25 grep $i $j | sed "s:$i = :_ss(\":g;s:$:\"):g" ; 26 26 done; 27 27 done > locale/.cache/my_service_string_to_translate.c … … 33 33 34 34 #!/bin/bash 35 xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ 35 xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ss 36 36 37 37 Once 'messages.po' is created, use the following command to create the po file for the targeted language for translation. We will use the French language here as an example : … … 45 45 Edit the zoo_fr_FR.po file with your favorite text editor or using one of the following tools : 46 46 47 * [http://www.poedit.net/ poedit]48 * [http://translate.sourceforge.net/wiki/virtaal/index virtaal]49 * [https://www.transifex.net/projects/p/grass6/c/grass64/ transifex]47 * `poedit <http://www.poedit.net/>`__ 48 * `virtaal <http://translate.sourceforge.net/wiki/virtaal/index>`__ 49 * `transifex <https://www.transifex.net/>`__ 50 50 51 51 Once the zoo_fr_FR.po file is completed, you can generate and install the corresponding *mo* file using the following command : … … 61 61 example, such a request: 62 62 63 [http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS] 63 http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS 64 64 65 65 would become the following: 66 66 67 [http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR] 67 http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR 68 68 69 69 The following command may also be useful in order to pull all the translations already available for a specific language. -
branches/PublicaMundi_David-devel/docs/index.rst
r695 r696 22 22 23 23 .. image:: _static/by-sa.png 24 :height: 141px 25 :width: 403px 24 :width: 103px 26 25 :scale: 50 % 27 26 :alt: CC-BY-SA license -
branches/PublicaMundi_David-devel/docs/install/download.rst
- Property svn:keywords set to Date Author
r695 r696 19 19 :: 20 20 21 svn checkout http://svn.zoo-project.org/svn/trunk zoo- project21 svn checkout http://svn.zoo-project.org/svn/trunk zoo-src 22 22 23 23 Registered ZOO-Project developers would prefer the following: … … 26 26 27 27 sed "s:\[tunnels\]:\[tunnels\]\nzoosvn = /usr/bin/ssh -p 1046:g" -i ~/.subversion/config 28 svn co svn+zoosvn://svn.zoo-project.org/var/svn/repos/trunk zoo- project28 svn co svn+zoosvn://svn.zoo-project.org/var/svn/repos/trunk zoo-src 29 29 30 30 .. note:: -
branches/PublicaMundi_David-devel/docs/install/index.rst
- Property svn:keywords set to Date Author
r684 r696 10 10 :maxdepth: 2 11 11 12 install-prerequisites 13 install-download 14 install-confoptions 15 install-installation 16 install-onwindows 12 prerequisites 13 download 14 installation 15 debian 16 opensuse 17 centos 18 windows 17 19 18 20 -
branches/PublicaMundi_David-devel/docs/install/installation.rst
- Property svn:keywords set to Date Author
r695 r696 2 2 3 3 Installation on Unix/Linux 4 ================= 4 ========================== 5 6 To build and install ZOO-Project on your Web Server you will need 4 7 steps : 8 9 * build the cgic library, 10 * install the ZOO-Kernel, 11 * install the ZOO-Services, 12 * testing your installation. 13 14 Build cgic 15 ---------- 16 17 Run the following commands from the ``thirds/cgic`` directory to build 18 the cgic library. 19 20 :: 21 22 cd thirds/cgic 23 make 24 25 The cgic library originaly come from `http://www.boutell.com/cgic 26 <http://www.boutell.com/cgic>`_. 27 28 .. warning:: 29 30 You may need to edit the ``Makefile`` in case you are using a 64 bits 31 platform for building and your fcgi library is not located in ``/usr/lib64``. 32 33 Install the ZOO-Kernel 34 ---------------------- 35 5 36 6 37 For the impatient 7 -------------- 38 ................. 8 39 9 40 Run the following commands from the directory where you :ref:`install-download` and extracted the ZOO Kernel source code in order to build the ``zoo_loader.cgi`` CGI program with default options. … … 11 42 :: 12 43 13 cd zoo- kernel44 cd zoo-project/zoo-kernel 14 45 autoconf 15 46 ./configure 16 47 make 17 18 This should produce executables for the *zoo_loader.cgi* CGI program in the ``zoo-kernel`` directory. Copy the *zoo_loader.cgi* and *main.cfg* files to the HTTP server ``cgi`` directory and start using it. 48 make install 49 50 This should produce executables for the *zoo_loader.cgi* CGI program 51 (located per default in ``/usr/lib/cgi-bin/``) and a shared library 52 ``libzoo_service`` (located per default in ``/usr/local/lib``). 19 53 20 54 .. warning:: 21 55 22 Edit ZOO-Kernel installation settings in the *main.cfg* file (set ``tmpPath`` and ``tmpUrl`` to fit your web server configuration). 23 24 Debian / Ubuntu 25 ---------------------- 26 27 Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on Debian or Ubuntu distributions. 28 29 Prerequisites 30 ...................... 31 32 Using Debian 33 ********************** 34 35 The following command should install all the required dependancies on Debian. See the :ref:`install-prereq` section for additional information. 36 37 .. code-block:: guess 38 39 apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion python-dev libgdal1-dev build-essential libmozjs185-dev 40 41 Using Ubuntu 42 ********************** 43 44 On Ubuntu, use the following command first to install the required dependancies : 45 46 .. code-block:: guess 47 48 sudo apt-get install flex bison libfcgi-dev libxml2 libxml2-dev curl openssl autoconf apache2 python-software-properties subversion libmozjs185-dev python-dev build-essential 49 50 Then add the *UbuntuGIS* repository in order to get the latest versions of libraries 51 52 .. code-block:: guess 53 54 sudo add-apt-repository ppa:ubuntugis/ppa 55 sudo apt-get update 56 57 Install the geographic library as follow: 58 59 .. code-block:: guess 60 61 sudo apt-get install libgdal1-dev 62 63 64 Installation 65 ...................... 66 67 :ref:`install-download` ZOO-Project latest version from svn using the following command: 68 69 .. code-block:: guess 70 71 svn checkout http://svn.zoo-project.org/svn/trunk zoo-project 72 73 Install the *cgic* library from packages using the following command: 74 75 .. code-block:: guess 76 77 cd zoo-project/thirds/cgic206/ 78 make 79 80 Head to the :ref:`kernel_index` directory 81 82 .. code-block:: guess 83 84 cd ../../zoo-project/zoo-kernel/ 85 86 Create a configure file as follow: 87 88 .. code-block:: guess 89 90 autoconf 91 92 Run configure with the desired options, for example with the following command: 93 94 .. code-block:: guess 95 96 ./configure --with-js --with-python 56 Edit ZOO-Kernel installation settings in the ``main.cfg`` file (set 57 ``tmpPath`` and ``tmpUrl`` to fit your web server configuration). 58 59 60 Configure options 61 ................. 62 63 This section provides information on :ref:`kernel_index` configure options. It is recommanded to also read the :ref:`kernel_config` section for configuration technical details. 64 65 Here is the list of available options as returned by ``./configure --help`` command: 66 67 .. list-table:: Configure Options 68 :header-rows: 1 69 70 * - Option 71 - Description 72 * - ``--with-cgi-dir=PATH`` 73 - Specifies an alternative cgi directory path (default: 74 /usr/lib/cgi-bin) 75 * - ``--with-db-backend`` 76 - Relies on a database for storing status messages and response 77 files 78 * - ``--with-yaml=PATH`` 79 - Specifies an alternative location for the yaml library 80 * - ``--with-fastcgi=PATH`` 81 - Specifies an alternative location for the fastcgi library 82 * - ``--with-gdal-config=FILE`` 83 - Specifies an alternative gdal-config file 84 * - ``--with-xml2config=FILE`` 85 - Specifies an alternative xml2-config file 86 * - ``--with-python=PATH`` 87 - Enables python support or specifies an alternative directory 88 for python installation (disabled by default) 89 * - ``--with-pyvers=NUM`` 90 - Uses a specific python version 91 * - ``--with-js=PATH`` 92 - Enables javascript support, disabled by default 93 * - ``--with-php=PATH`` 94 - Enables php support or specify an alternative directory for php 95 installation, disabled by default 96 * - ``--with-java=PATH`` 97 - Enables java support or specifies a JDK_HOME, disabled by 98 default 99 * - ``--with-ruby=PATH`` 100 - To enable ruby support or specify an alternative directory for 101 ruby installation, disabled by default 102 * - ``--with-rvers=NUM`` 103 - To use a specific ruby version 104 * - ``--with-perl=PATH`` 105 - Enables perl support or specifies an alternative directory for 106 perl installation, disabled by default 107 * - ``--with-mapserver=PATH`` 108 - Specifies the path for MapServer compiled source tree 109 * - ``--with-itk=PATH`` 110 - Specifies an alternative location for the ITK library 111 * - ``--with-itk-version=VERSION`` 112 - Specifies an alternative version for the ITK library 113 * - ``--with-otb=PATH`` 114 - Enables optional OrfeoToolbox support 115 * - ``--with-wx-config=PATH`` 116 - Specifies an alternative path for the wx-config tool 117 * - ``--with-saga=PATH`` 118 - Enables optional SAGA GIS support 119 120 121 .. code :: 122 123 --with-cgi-dir=PATH Specifies an alternative cgi directory path ( 124 default: /usr/lib/cgi-bin) 125 --with-db-backend Relies on a database for storing status messages and 126 response files 127 --with-yaml=PATH Specifies an alternative location for the yaml 128 library 129 --with-fastcgi=PATH Specifies an alternative location for the fastcgi 130 library 131 --with-xml2config=FILE Specifies an alternative xml2-config file 132 --with-xsltconfig=FILE Specifies an alternative xslt-config file 133 --with-gdal-config=FILE Specifies an alternative gdal-config file 134 --with-proj=PATH Specifies an alternative location for PROJ4 setup 135 --with-geosconfig=FILE Specifies an alternative geos-config file 136 --with-cgal=PATH Specifies an alternative location for CGAL setup 137 --with-mapserver=PATH Specifies the path for MapServer compiled source 138 tree 139 --with-python=PATH To enable python support or Specifies an alternative 140 directory for python installation, disabled by 141 default 142 --with-pyvers=NUM To use a specific python version 143 --with-js=PATH Specifies --with-js=path-to-js to enable js support, 144 specify --with-js on linux debian like, js support 145 is disabled by default 146 --with-php=PATH To enable php support or specify an alternative 147 directory for php installation, disabled by default 148 --with-java=PATH To enable java support, specify a JDK_HOME, disabled 149 by default 150 --with-ruby=PATH To enable ruby support or specify an alternative 151 directory for ruby installation, disabled by default 152 --with-rvers=NUM To use a specific ruby version 153 --with-perl=PATH To enable perl support or specify an alternative 154 directory for perl installation, disabled by default 155 --with-itk=PATH Specifies an alternative location for the itk 156 library 157 --with-itk-version=VERSION 158 Specifies an alternative version for the itk library 159 --with-otb=PATH Specifies an alternative location for the otb 160 library 161 --with-wx-config=PATH Specifies an alternative path for the wx-config tool 162 --with-saga=PATH Specifies an alternative location for the SAGA-GIS 163 library 164 165 166 167 168 :: 169 170 --with-cgi-dir=PATH Specifies an alternative cgi directory path (default: /usr/lib/cgi-bin) 171 --with-db-backend Relies on a database for storing status messages and response files 172 --with-yaml=PATH Specifies an alternative location for the yaml library 173 --with-fastcgi=PATH Specifies an alternative location for the fastcgi library 174 --with-gdal-config=FILE Specifies an alternative gdal-config file 175 --with-xml2config=FILE Specifies an alternative xml2-config file 176 --with-python=PATH Enables python support or specifies an alternative directory for python installation (disabled by default) 177 --with-pyvers=NUM Uses a specific python version 178 --with-js=PATH Enables javascript support, disabled by default 179 --with-php=PATH Enables php support or specify an alternative directory for php installation, disabled by default 180 --with-java=PATH Enables java support or specifies a JDK_HOME, disabled by default 181 --with-ruby=PATH To enable ruby support or specify an alternative directory for ruby installation, disabled by default 182 --with-rvers=NUM To use a specific ruby version 183 --with-perl=PATH Enables perl support or specifies an alternative directory for perl installation, disabled by default 184 --with-mapserver=PATH Specifies the path for MapServer compiled source tree 185 --with-itk=PATH Specifies an alternative location for the ITK library 186 --with-itk-version=VERSION Specifies an alternative version for the ITK library 187 --with-otb=PATH Enables optional OrfeoToolbox support 188 --with-wx-config=PATH Specifies an alternative path for the wx-config tool 189 --with-saga=PATH Enables optional SAGA GIS support 190 191 All the options are described in more details in the following sections. 192 193 GDAL Support (Required) 194 ........................ 195 196 If gdal-config program is not found in your ``PATH``, a 197 ``--with-gdal-config`` option can be used to specify its location. For 198 instance, if ``gdal-config`` lies in ``/usr/local/bin`` which is not in 199 your PATH, you may use the following command: 200 201 :: 202 203 $ ./configure --with-gdal-config=/usr/local/bin/gdal-config 204 205 XML2 Support (Required) 206 ........................ 207 208 If xml2-config program is not found in PATH, a *--with-xml2config* option can be used to specify its location. For instance, if xml2-config is installed in ``/usr/local/bin`` which is not in PATH, you may use the following command: 209 210 :: 211 212 $ ./configure --with-xml2config=/usr/local/bin/xml2-config 213 214 215 Python Support (Optional) 216 .............................................. 217 218 The ``--with-python=yes`` option is required to activate the :ref:`kernel_index` Python support, using the following command: 219 220 :: 221 222 $ ./configure --with-python=yes 223 224 This assumes that python-config is found in your ``PATH``. If not, 225 then you can specify the Python installation directory using the 226 following command (with Python installed in the ``/usr/local`` 227 directory): 228 229 :: 230 231 $ ./configure --with-python=/usr/local 232 233 234 Python Version 235 ************** 236 237 If multiple Python versions are available and you want to use a 238 specific one, then you can use the ``--with-pyvers`` option as shown 239 bellow: 240 241 :: 242 243 $ ./configure --with-pyvers=2.7 244 245 246 PHP Support (Optional) 247 .............................................. 248 249 The ``--with-php=yes`` option is required to activate the 250 :ref:`kernel_index` PHP support`, using the following command: 251 252 :: 253 254 $ ./configure --with-php=yes 255 256 This assumes that ``php-config`` can be found in the ``<PATH>/bin`` 257 directory . So, supposing the your ``php-config`` can be found in 258 ``/usr/local/bin``, then use the following command: 259 260 :: 261 262 $ ./configure --with-php=/usr/local 263 264 .. warning:: 265 ZOO-Kernel optional PHP support requires a local PHP Embedded installation. Read more `here <http://zoo-project.org/trac/wiki/ZooKernel/Embed/PHP>`__. 266 267 268 Perl Support (Optional) 269 .............................................. 270 271 The ``--with-perl=yes`` option can be used for activating the 272 ZOO-Kernel Perl support, as follow: 273 274 :: 275 276 $ ./configure --with-perl=yes 277 278 This assumes that perl is found in your PATH. For instance, if Perl is 279 installed in ``/usr/local`` and ``/usr/local/bin`` is not found in 280 your ``PATH``, then the following command can be used (this assumes 281 that ``/usr/local/bin/perl`` exists): 282 283 :: 284 285 $ ./configure --with-perl=/usr/local 286 287 288 Java Support (Optional) 289 .............................................. 290 291 In order to activate the Java support for ZOO-Kernel, the 292 `--with-java` configure option must be specified and sets the 293 installation path of your Java SDK. For instance, if Java SDK is 294 installed in the ``/usr/lib/jvm/java-6-sun-1.6.0.22/`` directory, 295 then the following command can be used: 296 297 :: 298 299 $ ./configure --with-java=/usr/lib/jvm/java-6-sun-1.6.0.22/ 300 301 This assumes that the ``include/linux`` and ``jre/lib/i386/client/`` 302 subdirectories exist in ``/usr/lib/jvm/java-6-sun-1.6.0.22/``, and 303 that the ``include/linux`` directory contains the ``jni.h`` headers file 304 and that the ``jre/lib/i386/client/`` directory contains the ``libjvm.so`` 305 file. 306 307 308 .. note:: 309 With Mac OS X you only have to set *macos* as the value for the 310 ``--with-java`` option to activate Java support. For example: 311 312 :: 313 314 $ ./configure --with-java=macos 315 316 .. _js-support: 317 318 JavaScript Support (Optional) 319 .............................................. 320 321 In order to activate the JavaScript support for ZOO-Kernel, 322 the ``--with-js=yes`` configure option must be specified. If you are using 323 a "Debian-like" GNU/Linux distribution then dpkg will be used to 324 detect if the required packages are installed and you don't have to 325 specify anything here. The following command is only needed (assuming 326 that js_api.h and libmozjs.so are found in default directories): 327 328 329 :: 330 331 $ ./configure --with-js=yes 332 333 If you want to use a custom installation of `SpiderMonkey 334 <https://developer.mozilla.org/en/SpiderMonkey>`__ , or if you are not 335 using a Debian packaging system, then you'll have to specify the 336 directory where it is installed. For instance, if SpiderMonkey is in 337 ``/usr/local/``, then the following command must be used: 338 339 :: 340 341 $ ./configure --with-js=/usr/local 342 343 344 MapServer Support (Optional) 345 .............................................. 346 347 348 In order to activate the WMS, WFS and WCS output support using 349 MapServer, the ``--with-mapserver`` option must be used. The path to 350 ``mapserver-config`` which is located in the source code of MapServer 351 must also be set, using the following command: 352 353 :: 354 355 $ ./configure --with-mapserver=/path/to/your/mapserver_config/ 356 357 358 Read more about the :ref:`kernel-mapserver`. 359 360 361 Orfeo Toolbox Support (Optional) 362 ..................................................... 363 364 In order to activate the optional Orfeo Toolbox support, the 365 ``--with-otb`` option must be used, using the following command: 366 367 :: 368 369 $ ./configure --with-otb=/path/to/your/otb/ 370 371 372 Read more about the :ref:`kernel-orfeotoolbox`. 373 374 .. warning:: 375 To build the Orfeo Toolbox support you will require ITK, the 376 default version of ITK is 4.5, in case you use another version, 377 please make sure to use the ``--with-itk-version`` to specificy 378 what is the version available on your system. 379 380 SAGA GIS Support (Optional) 381 ..................................................... 382 383 384 In order to activate the optional SAGA GIS support, the *--with-saga* option must be used, using the following command: 385 386 :: 387 388 $ ./configure --with-saga=/path/to/your/saga/ 389 390 391 Read more about the :ref:`kernel-sagagis`. 392 393 .. warning:: 394 In case wx-config is not in your ``PATH`` please, make sure to use 395 the ``--with-wx-config`` to specify its location. 396 397 Install ZOO-Services 398 -------------------- 399 400 .. warning:: 401 We present here a global installation procedure for basics 402 ZOO-Services, for details about automatic installation of services 403 provided by :ref:`kernel-orfeotoolbox` or :ref:`kernel-sagagis`, 404 please refer to there specific documentations. 405 406 Depending on the programming language used to implement the 407 ZOO-Services you want to install, you will need to build a 408 Services Provider. In the case of *C* and *Fotran*, you would create a 409 shared library exporting the functions corresponding to all the 410 ZOO-Services provided by this Services Provider. In case of *Java*, 411 you will need to build a Java Class. In any other programming 412 language, you should simply have to install the ServiceProvider and 413 the zcfg files. 414 415 If building a Shared library or a Java class is required, then you 416 should find a ``Makefile`` in the service directory which is 417 responsible to help you build this Services Provider. So you should 418 simply run the `make` command from the Service directory to generate 419 the required file. 420 421 Then you simply need to copy the content of the ``cgi-env`` directory 422 in ``cgi-bin``. 423 424 To install the ``ogr/base-vect-ops`` Services Provider, supposing that 425 your ``cgi-bin`` directory is ``/usr/local/lib`` use the following 426 commands: 427 428 .. code:: 429 430 cd zoo-project/zoo-services/ogr/base-vect-ops 431 make 432 cp cgi-env/*.* /usr/lib/cgi-bin 97 433 98 434 .. note:: 99 Refer to the :ref:`install-configure` section for the full list of available options 100 101 Compile ZOO-Kernel as follow: 102 103 .. code-block:: guess 104 105 make 106 107 Copy the necessary files to the `cgi-bin` directory (as administrator user) 108 109 .. code-block:: guess 110 111 cp main.cfg /usr/lib/cgi-bin 112 cp zoo_loader.cgi /usr/lib/cgi-bin 113 114 Install ZOO ServiceProviders, for example the basic Python service (as administrator user) 115 116 .. code-block:: guess 117 118 cp ../zoo-services/hello-py/cgi-env/*.zcfg /usr/lib/cgi-bin 119 cp ../zoo-services/hello-py/*.py /usr/lib/cgi-bin/ 120 121 Edit the *main.cfg* file as follow (example configuration): 122 123 .. code-block:: guess 124 125 nano /usr/lib/cgi-bin/main.cfg 126 - serverAddress = http://127.0.0.1 127 128 129 Test the ZOO-Kernel installation with the following requests: 130 131 .. code-block:: guess 132 133 http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=GetCapabilities&Version=1.0.0 134 135 .. code-block:: guess 136 137 http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=DescribeProcess&Version=1.0.0&Identifier=HelloPy 138 139 .. code-block:: guess 140 141 http://127.0.0.1/cgi-bin/zoo_loader.cgi?ServiceProvider=&metapath=&Service=WPS&Request=Execute&Version=1.0.0&Identifier=HelloPy&DataInputs=a=myname 142 143 144 .. note:: 145 146 Such request should return well formed XML documents (OWS documents responses). 147 148 .. warning:: 149 150 If ZOO-Kernel returns an error please check the :ref:`kernel_config` and beware of the :ref:`install-prereq`. 151 152 153 OpenSUSE 154 ---------------------- 155 156 :ref:`kernel_index` is maintained as a package in `OpenSUSE Build Service (OBS) <https://build.opensuse.org/package/show?package=zoo-kernel&project=Application%3AGeo>`__. RPM are thus provided for all versions of OpenSUSE Linux (11.2, 11.3, 11.4, Factory). 157 158 Stable release 159 ...................... 160 161 Use the following instructions to install ZOO-Project latetst release on OpenSUSE distribution. 162 163 One-click installer 164 ******************* 165 166 A one-click installer is available `here <http://software.opensuse.org/search?q=zoo-kernel&baseproject=openSUSE%3A11.4&lang=en&exclude_debug=true>`__. 167 For openSUSE 11.4, follow this direct `link <http://software.opensuse.org/ymp/Application:Geo/openSUSE_11.4/zoo-kernel.ymp?base=openSUSE%3A11.4&query=zoo-kernel>`__. 168 169 Yast software manager 170 ********************* 171 172 Add the `Application:Geo <http://download.opensuse.org/repositories/Application:/Geo/>`__ repository to the software repositories and then ZOO-Kernel can then be found in Software Management using the provided search tool. 173 174 Command line (as root for openSUSE 11.4) 175 **************************************** 176 177 Install ZOO-Kernel package by yourself using the following command: 178 179 .. code-block:: guess 180 181 zypper ar http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/ 182 zypper refresh 183 zypper install zoo-kernel 184 185 Developement version 186 ...................... 187 188 The latest development version of ZOO-Kernel can be found in OBS under the project `home:tzotsos <https://build.opensuse.org/project/show?project=home%3Atzotsos>`__. ZOO-Kernel packages are maintained and tested there before being released to the Application:Geo repository. Installation methods are identical as for the stable version. Make sure to use `this <http://download.opensuse.org/repositories/home:/tzotsos/>`__ repository instead. 189 190 Command line (as root for openSUSE 11.4) 191 ******************************************** 192 193 Install latest ZOO-Kernel trunk version with the following command: 194 195 .. code-block:: guess 196 197 zypper ar http://download.opensuse.org/repositories/home:/tzotsos/openSUSE_11.4/ 198 zypper refresh 199 zypper install zoo-kernel 200 zypper install zoo-kernel-grass-bridge 201 202 Note that there is the option of adding the zoo-wps-grass-bridge package. This option will automatically install grass7 (svn trunk). 203 204 205 CentOS 206 ---------------------- 207 208 Use the following instructions to install `ZOO-Project <http://zoo-project.org>`__ on CentOS distributions. 209 210 Prerequisites 211 ...................... 212 213 .. code-block:: guess 214 215 yum install apache2 216 yum install build-essentials 217 yum install gcc-c++ 218 yum install zlib-devel 219 yum install libxml2-devel 220 yum install bison 221 yum install openssl 222 yum install python-devel 223 yum install subversion 224 225 226 Compile then install FastCGI library from source 227 228 :: 229 230 wget http://www.fastcgi.com/dist/fcgi.tar.gz 231 tar xzf fcgi-2.4.0.tar.gz 232 ./configure 233 make 234 make install 235 echo /usr/local/lib >> /etc/ld.so.conf.d/local.conf 236 ldconfig 237 238 Compile then install the autoconf tools : 239 240 :: 241 242 wget http://ftp.gnu.org/gnu/autoconf/autoconf-latest.tar.gz 243 tar xzf autoconf-latest.tar.gz 244 ./configure --prefix=/usr 245 make 246 make install 247 248 Compile then install the flex tool : 249 250 :: 251 252 wget http://downloads.sourceforge.net/project/flex/flex/flex-2.5.35/flex-2.5.35.tar.gz?r=http%3A%2F%2Fflex.sourceforge.net%2F&ts=1292529005&use_mirror=switch 253 tar xzf flex-2.5.35.tar.gz 254 cd flex-2.5.35 255 ./configure --prefix=/usr 256 make 257 make install 258 259 Using the curl provided in the CentOS distribution will produce a ZOO-Kernel unable to run any 260 Service. Indeed, some segmentation faults occur when trying to run ``Execute`` requests on the ZOO-Kernel, 261 compiling the ZOO-Kernel setting ``USE_GDB`` flag in the ``CFLAGS`` of your ``Makefile`` will let you run 262 ZOO-Kernel from gdb and be able to get more information on what is going wrong with your ZOO-Kernel. 263 Doing this we can figure out that code on `line 173 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L173>`__ 264 and `line 175 <http://zoo-project.org/trac/browser/trunk/zoo-kernel/ulinet.c#L175>`__ have to be commented in the 265 ``ulinet.c`` file to get a ZOO-Kernel working using the curl available in CentOS (curl version 7.15.5). 266 If you don't apply the modification, you will get an error from a gdb session pointing 267 segfault in ``Curl_cookie_clearall``. 268 269 You can optionally compile then install curl from source : 270 271 :: 272 273 wget http://curl.haxx.se/download/curl-7.21.3.tar.bz2 274 tar xjf curl-7.21.3.tar.bz2 275 cd curl-7.21.3 276 ./configure --prefix=/usr 277 make 278 make install 279 280 Compile then install Python : 281 282 :: 283 284 wget http://www.python.org/ftp/python/2.6.6/Python-2.6.6.tar.bz2 285 tar xjf Python-2.6.6.tar.bz2 286 cd Python-2.6.6 287 ./configure 288 make 289 make install 290 291 Compile then install your own GDAL library : 292 293 :: 294 295 wget http://download.osgeo.org/gdal/gdal-1.7.3.tar.gz 296 tar xzf gdal-1.7.3.tar.gz 297 cd gdal-1.7.3 298 ./configure # add your options here 299 make 300 make install 301 302 Install the Sun JAVA SDK into ``/usr/share`` then use the following command to ensure that the ``libjvm.so`` 303 will be found at runtime from any context. 304 305 :: 306 307 echo /usr/share/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client/ >> /etc/ld.so.conf.d/jvm.conf 308 ldconfig 309 435 You may also run ``make install`` directly after ``make``. 436 437 438 To install the hello-py Services Provider, use the following commands: 439 440 .. code:: 441 442 cd zoo-project/zoo-services/hello-py/ 443 cp cgi-env/* /usr/lib/cgi-bin 444 445 446 Testing your installation 447 ------------------------- 448 449 To test your installation yous should first be able to run the 450 following command from the ``cgi-bin`` directory: 451 452 .. code:: 453 454 ./zoo_loader.cgi "request=GetCapabilities&service=WPS" 455 456 -
branches/PublicaMundi_David-devel/docs/install/prerequisites.rst
- Property svn:keywords set to Date Author
r695 r696 10 10 11 11 - autoconf (`http://www.gnu.org/software/autoconf/ <http://www.gnu.org/software/autoconf/>`_) 12 - cgic (`http://www.boutell.com/cgic <http://www.boutell.com/cgic>`_)12 - gettext (`https://www.gnu.org/software/gettext/ <https://www.gnu.org/software/gettext/>`_ ) 13 13 - cURL (`http://curl.haxx.se <http://curl.haxx.se>`_ ) 14 14 - FastCGI (`http://www.fastcgi.com <http://www.fastcgi.com>`_ ) … … 16 16 - libxml2 ( http://xmlsoft.org ) 17 17 - OpenSSL ( http://www.openssl.org ) 18 - Python ( http://www.python.org ) 19 - GDAL (for using the available GDAL based ZOO-Services) (http://gdal.org/) 18 - GDAL (http://gdal.org/) 20 19 21 20 .. warning:: … … 28 27 29 28 - MapServer (for ZOO-Kernel optional WMS, WFS and WCS support) (http://mapserver.org) 29 - Python ( http://www.python.org ) 30 30 - PHP Embedded (for ZOO-Kernel optional PHP support) (http://www.php.net) 31 31 - Java SDK (for ZOO-Kernel optional Java support) (http://java.sun.com) -
branches/PublicaMundi_David-devel/docs/install/windows.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/configuration.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/index.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/mapserver.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/orfeotoolbox.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/sagagis.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/kernel/what.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/debug.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/howtos.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/index.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/process-profiles.rst
- Property svn:keywords set to Date Author
r659 r696 2 2 3 3 Process profiles registry 4 ================ 4 ========================= 5 5 6 6 WPS Services belonging to the same Services provider often share the … … 9 9 this may be a waste of time to write them all. 10 10 11 :ref:`ZOO-Kernel <kernel_index>` is able to handle metadata inheritance from `rev. 607 <http://www.zoo-project.org/trac/changeset/607>`__, and this solves the issue of writing many ZCFG with same input and output. A registry can be loaded (before any other ZCFG files) and contain a set of Process Profiles organized in hierarchic levels according to the following rules: 11 :ref:`ZOO-Kernel <kernel_index>` is able to handle metadata 12 inheritance from `rev. 607 13 <http://www.zoo-project.org/trac/changeset/607>`__, and this solves 14 the issue of writing many ZCFG with same input and output. A registry 15 can be loaded (before any other ZCFG files) and contain a set of 16 Process Profiles organized in hierarchic levels according to the 17 following rules: 12 18 13 19 * *Concept*: The higher level in the hierarchy. *Concepts* are basic text files containing an abstract description of a WPS Service. … … 171 177 </Supported> 172 178 </DataOutputs> 179 -
branches/PublicaMundi_David-devel/docs/services/status.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/what.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/zcfg-reference.rst
- Property svn:keywords set to Date Author
-
branches/PublicaMundi_David-devel/docs/services/zoo-services.rst
- Property svn:keywords set to Date Author
Note: See TracChangeset
for help on using the changeset viewer.