Differences

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

--- en:user_advanced:installation_310 [2025/07/14 23:49] – kjdon
+++ en:user_advanced:installation_310 [2025/07/15 00:06] (current) – kjdon
@@ Line 1: / Line 1: @@
 ====== Advanced Installation : 3.10 and prior ======
 //Up to date for GS3.10, checked 20 Feb 2021.
 This page is up to date for 3.06 (5 November 2014). Much of it was checked again to be up to date after 3.08.//
+[[en:user_advanced:installation|Advanced Installation Index Page]] - from here you can access different versions of this page.
 For most users, the main Greenstone download (also called the "binary") with default settings is sufficient, and is very [[en:beginner:install_basic|easy to install]]. However, there are some instances where you may want or need to go through a more advanced installation process:
@@ Line 23: / Line 21: @@
-  * [[en:developer:compiling_greenstone|Compiling Greenstone]]
+  * [[en:developer:compiling_greenstone3|Compiling Greenstone3]]
@@ Line 326: / Line 324: @@
 **NOTE:** Previously, the instructions for running the installer in text-only mode were incorrect. They advised running the installer wrongly using ''./Greenstone-3.06rc1-linux-x64 text-only'', which rather triggered the default behaviour of the installer software (antinstaller) for a different kind of text-only installation rather than triggering the Greenstone installer's specific -textonly mode. Unfortunately, the wrong route would not install the bundled JRE into the Greenstone installation, despite requiring the Greenstone user to run the ''java'' command in the very next step of the install.
-===== 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.home}/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, so 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
--->
-===== Moving a Greenstone installation =====
-For Linux, you will need to uninstall your Greenstone first and then reinstall it in the new location.
-For Windows:
-In the case of GS2.83, if you move your Greenstone2 installation folder to some other location, make sure that you relocate it such that there are no spaces in its new path. For instance, "C:\Program Files\myfolder\greenstone2" contains a space between "Program" and "Files", which is not supported in version 2.83. In future versions of Greenstone, the spaces will not be a problem.
-Once you've moved your Greenstone installation, there are a few further things to do to get it to work again:
-  - Open your Greenstone 2 installation's cgi-bin\gsdlsite.cfg file and change the value for the GSDLHOME property to reflect the new path to your Greenstone installation.
-  - To get the local library server (server.exe) to work from the new location: if your top-level Greenstone installation folder contains the files llssite.cfg and glisite.cfg, delete these. (Note that you should not delete the template files llssite.cfg.in and glisite.cfg.in!) If running the local library server has any issues with Internet Explorer, go to the local library's File>Settings menu and change the Other Browser setting to use Firefox.
-  - To get the Apache web server included with Greenstone to work: delete the file lib\java\log4j.properties. (Doing so will ensure that if you execute the gs2-server.bat file--which launches the Greenstone Server Interface--this properties file will be regenerated with the correct value for gsdlhome.)