Differences

This shows you the differences between two versions of the page.

--- en:user_advanced:installation [2018/03/27 05:25] – [Uptodate source code from SVN] anupama
+++ en:user_advanced:installation [2018/06/26 09:18] – [Uptodate source code from SVN] anupama
@@ Line 19: / Line 19: @@
   * [[en:developer:compiling_greenstone|Compiling Greenstone]]
-==== Installation for a networked lab environment ====
-To support use of Greenstone 3 in a networked lab environment, it is possible to adjust the configuration settings of the installation to have one shared installation of the software, but allow individual
-users to build and serve collections from their own area of the file system.  We refer to this as a "dispersed GS3" setup.
-More specifically, it is appropriate for a situation where your Greenstone 3 is to be distributed across 3 locations of your Windows machine: an installation location which is read-only regular users, and to which only the administrator has write permissions; a user-web location that is writable and specific to a user; and a temporary (typically local) file system area the user has read/write permissions to.
-In the following text we describe the setup procedure for Windows, with
-Greenstone installed in C:/Program Files/.  The same capability will work in networked situations
-for MacOS and Linux labs, choosing an appropriate directory such as /usr/local/Greenstone3
-as the location to install the GS3 software to.
-For one computer, here's how you can have Greenstone installed centrally (e.g. Program Files), but then have each different user when working at that computer have their own instance of the Greenstone 3 sites, collections, and customisations of the interface.
-Install GS3 as an administrator using the binary installer. Then set the following 4 properties in build.properties:
-  * set ''using.user.web=true''
-  * set ''web.home=${user.home}/greenstone3/web''\\ [[https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html|Java's user.home property]] should resolve to a writable user location, e.g  web.home will work out to be something like C:/Users/me/greenstone3/web). You can decide on other locations within ${user.home}, as you choose. For example, you can set web.home=${user.web}/gs3/myweb. \\ Or if your lab setup is such that you're mounting each user's account at H: at each log in, then just set web.home=H:/gs3/web. Then, whenever any user is logged in, their collection data will be in H:/gs3/web. So web.home in such a case may look static and fixed to somewhere in H: in the build.properties file, but it's actually not static, since it changes to refer to different users' accounts based on who is logged in.
-  * set ''gsdl3home.isreadonly=true''
-  * set ''gsdl3.writablehome=${java.io.tmpdir}/greenstone/web''
-Set all the property values exactly as above, except ''web.home'', which you should customise to point to a location that is writable by the GS3 user where the user can create collections. File path separators should be URL style slashes (forward slash, /).
-Now if you replicate the installation to other machines in the lab, your users can log into any machine and continue working with Greenstone3.
-<!--
-greenstone-307.cmd file contains:
-@goto %1
-:start
-robocopy /e /purge /np image "C:\Program Files\Greenstone3" /log:image.log
-if %ERRORLEVEL% GEQ 4 fail
-robocopy /e /xx /np patches "C:\Program Files\Greenstone3" /log:patches.log
-if %ERRORLEVEL% GEQ 4 fail
-robocopy /e /purge /np startmenu "%ALLUSERSPROFILE%\Start Menu\Programs\Greenstone 3" /log:startmenu.log
-if %ERRORLEVEL% GEQ 4 fail
-done
--->
-==== Running the installer in text-only mode ====
-  - If you're on Linux or Mac, give the binary of the installer execute permissions
-  - Then run it by passing in the text-only flag, as shown below.
-  - Follow the instructions on the screen thereafter. If you mistype at any stage, press ctrl-C to start again.
-<code>
-> ./Greenstone-3.06rc1-linux-x64 text-only
-----------------------------
-Extracting java installer...
-----------------------------
-Extraction Complete
-You can now run "java -jar greenstone.jar text" to run the installer from the command line
->
-</code>
 ===== Windows =====
@@ Line 448: / Line 386: @@
 export JAVA_HOME=/path/to/your/jdk7
 export ANT_HOME=/path/to/your/ant
-export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH
+export PATH=$JAVA_HOME/bin:
+$ANT_HOME/bin:$PATH
 </code>
   - Checkout the code: <code>
@@ Line 456: / Line 395: @@
 ant
 </code>\\ Now, if necessary, you can customise the port/hostname fields in the newly generated toplevel file ''build.properties''.
-  - Most Linux systems and probably all the newer Mac systems require //gnome-lib// for successful compilation. Uncomment the following to activate it <code>
+  - Most Linux systems and probably all the newer Mac systems require //gnome-lib// for successful compilation. If you wish to //compile gnome-lib// along with GS3, uncomment the following line in ''build.properties'' to activate it <code>
 checkout.gnomelib.ext=true
-</code>
+</code>\\ Skip this step if you don't want to //compile// the gnome-lib extension when compiling GS3, but prefer to use a pre-compiled ''gnome-lib'' to speed up the process, in which case you'll carry out step 9 later.
   - If you want to compile imagemagick from source on Unix systems (though for Mac you can also use the precompiled imagemagick binary*), <code>
 checkout.imagemagick.ext=true
@@ Line 465: / Line 404: @@
 export CXXFLAGS="$CXXFLAGS $CFLAGS"
 export JNICFLAGS="$JNICFLAGS $CFLAGS"</code> Since GS3.08, if you're on 64 bit linux, you will also need to add -fPIC to the CFLAGS environment variable: \\ <code>export CFLAGS="-fPIC $CFLAGS"</code>
-  - Finally, you can start the steps for compiling: <code>
+  - Finally, you can start the steps for building GS3 from SVN: <code>
-ant prepare
+ant prepare</code>
-</code><!--<code>
+  - If you had determined to use a pre-compiled gnome-lib in step 5, then visit http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk and there click on the link for the ''gnome-lib-**minimal**-'' zip/tarball for your operating system. On the next page, click on the download link to download the zip/tarball file, then move this downloaded file into ''gs2build/ext''. After that, unpack and set up your gnome-lib-minimal for compiling as follows: \\ <code>cd gs2build/ext
+tar -xvzf gnome-lib-minimal-<your-OS-version>.tar.gz
+cd gnome-lib-minimal
+source ./devel.bash
+cd ../../..
+</code>
+  - You can now run the compile step: <!--<code>
 cd ext
 source devel.bash
@@ Line 506: / Line 451: @@
 For more detailed instructions on installation, please refer to the [[en:developer:linux_source_install|Linux]]
 and [[en:developer:mac_source_install|Mac OS]] source installation pages.
+==== Running the installer in text-only mode ====
+  - If you're on Linux or Mac, give the binary of the installer execute permissions
+  - Then run it by passing in the text-only flag, as shown below.
+  - Follow the instructions on the screen thereafter. If you mistype at any stage, press ctrl-C to start again.
+<code>
+> ./Greenstone-3.06rc1-linux-x64 text-only
+----------------------------
+Extracting java installer...
+----------------------------
+Extraction Complete
+You can now run "java -jar greenstone.jar text" to run the installer from the command line
+>
+</code>
+===== Installation for a networked lab environment =====
+To support use of Greenstone 3 in a networked lab environment, it is possible to adjust the configuration settings of the installation to have one shared installation of the software, but allow individual
+users to build and serve collections from their own area of the file system.  We refer to this as a "dispersed GS3" setup.
+More specifically, it is appropriate for a situation where your Greenstone 3 is to be distributed across 3 locations of your Windows machine: an installation location which is read-only regular users, and to which only the administrator has write permissions; a user-web location that is writable and specific to a user; and a temporary (typically local) file system area the user has read/write permissions to.
+In the following text we describe the setup procedure for Windows, with
+Greenstone installed in C:/Program Files/.  The same capability will work in networked situations
+for MacOS and Linux labs, choosing an appropriate directory such as /usr/local/Greenstone3
+as the location to install the GS3 software to.
+For one computer, here's how you can have Greenstone installed centrally (e.g. Program Files), but then have each different user when working at that computer have their own instance of the Greenstone 3 sites, collections, and customisations of the interface.
+Install GS3 as an administrator using the binary installer. Then set the following 4 properties in build.properties:
+  * set ''using.user.web=true''
+  * set ''web.home=${user.home}/greenstone3/web''\\ [[https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html|Java's user.home property]] should resolve to a writable user location, e.g  web.home will work out to be something like C:/Users/me/greenstone3/web). You can decide on other locations within ${user.home}, as you choose. For example, you can set web.home=${user.web}/gs3/myweb. \\ Or if your lab setup is such that you're mounting each user's account at H: at each log in, then just set web.home=H:/gs3/web. Then, whenever any user is logged in, their collection data will be in H:/gs3/web. So web.home in such a case may look static and fixed to somewhere in H: in the build.properties file, but it's actually not static, since it changes to refer to different users' accounts based on who is logged in.
+  * set ''gsdl3home.isreadonly=true''
+  * set ''gsdl3.writablehome=${java.io.tmpdir}/greenstone/web''
+Set all the property values exactly as above, except ''web.home'', which you should customise to point to a location that is writable by the GS3 user where the user can create collections. File path separators should be URL style slashes (forward slash, /).
+Now if you replicate the installation to other machines in the lab, your users can log into any machine and continue working with Greenstone3.
+<!--
+greenstone-307.cmd file contains:
+@goto %1
+:start
+robocopy /e /purge /np image "C:\Program Files\Greenstone3" /log:image.log
+if %ERRORLEVEL% GEQ 4 fail
+robocopy /e /xx /np patches "C:\Program Files\Greenstone3" /log:patches.log
+if %ERRORLEVEL% GEQ 4 fail
+robocopy /e /purge /np startmenu "%ALLUSERSPROFILE%\Start Menu\Programs\Greenstone 3" /log:startmenu.log
+if %ERRORLEVEL% GEQ 4 fail
+done
+-->
 ===== Source Code Stability =====