From ef916b299211fd74c740551242b6d48090063733 Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Fri, 1 Oct 2010 16:00:49 -0400 Subject: [PATCH] expand section "Installation of Evergreen Staff Client Software"; --- 1.6/admin/StaffclientInstallation.xml | 666 +++++++++++++++++----------------- 1 file changed, 336 insertions(+), 330 deletions(-) diff --git a/1.6/admin/StaffclientInstallation.xml b/1.6/admin/StaffclientInstallation.xml index afedd07..fcf7809 100644 --- a/1.6/admin/StaffclientInstallation.xml +++ b/1.6/admin/StaffclientInstallation.xml @@ -1,12 +1,18 @@ - -
+ + + Installation of Evergreen Staff Client Software + + This section describes installation of the Evergreen Staff Client software. + + +
Installing the Staff Client The Staff Client is automatically built by default as part of the normal make install process for Evergreen server-side software. See the section to review details related to building the Staff Client in the final compile/link/install phase of the default Evergreen build process. See the section for help on manually building the Staff Client. Otherwise, continue with the following sections to install a pre-built Staff Client. Installing a Pre-Built Staff Client You can install the Staff Client from pre-built images and packages without actually having to first build it. Pre-built packages are currently available for Windows, MAC OS X, and Linux. If you need to manually build the Staff Client, see the section . - +
Installing on Windows A standard Microsoft Windows installer that contains the current version of the Staff Client is available from the downloads section of the Evergreen website at http://www.evergreen-ils.org/downloads.php. Download the staff client installer, then run it. A screen that looks similar to this should appear:
@@ -29,8 +35,8 @@
First, configure the server you would like to connect to in the Server section. For example, the PINES demo system is demo.gapines.org. After selecting a server, click the Re-Test Server button. Because this is the initial run of the staff client, the Workstation section in the upper-right states: Not yet configured for the specified server. The first thing that must be done to the Staff Client on every workstation is to assign it a workstation name. This is covered in the section . - - +
+
Installing on Mac OS X A Mac package that contains the current version of the Staff Client is available for use with XULRunner. @@ -93,26 +99,28 @@
Executing XULRunner - /Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client - + /Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/Evergreen_Staff_Client +
This command should exit quietly. A folder will be created, named /Applications/OpenILS, containing a launcher named open_ils_staff_client. - + Removing previously installed XULRunner versions - If you already have a newer version installed, per the release notes, you will need to remove the entire directory /Library/Frameworks/XUL.framework before downgrading. - In addition, you may also need to remove the previous file /Library/Receipts/xulrunner-ver-mak.pkg. - If there is no file /Library/Receipts/xulrunner-ver-mak.pkg (possibly in newer OSX releases) you need to flush the receiptdb file. - If you install a newer version over a previous (older) install, the older one is not removed but the symlinks get changed to the newer one. - First, get the package identifier, then purge/forget the build that was initially installed: -
- Purging previous build - - sudo pkgutil --pkgs > /tmp/pkgs.txt - sudo pkgutil --forget org.mozilla.xulrunner - -
- It may not be necessary to edit the file /Library/Receipts/InstallHistory.plist after deleting the folder XUL.framework. +
+ If you already have a newer version installed, per the release notes, you will need to remove the entire directory /Library/Frameworks/XUL.framework before downgrading. + In addition, you may also need to remove the previous file /Library/Receipts/xulrunner-ver-mak.pkg. + If there is no file /Library/Receipts/xulrunner-ver-mak.pkg (possibly in newer OSX releases) you need to flush the receiptdb file. + If you install a newer version over a previous (older) install, the older one is not removed but the symlinks get changed to the newer one. + First, get the package identifier, then purge/forget the build that was initially installed: +
+ Purging previous build + + sudo pkgutil --pkgs > /tmp/pkgs.txt + sudo pkgutil --forget org.mozilla.xulrunner + +
+ It may not be necessary to edit the file /Library/Receipts/InstallHistory.plist after deleting the folder XUL.framework. +
Creating an APP file: Staff Client & XULRunner Bundled @@ -120,21 +128,21 @@
Sample APP file folder structure - * Evergreen.app - * Contents - * Frameworks - * Resources - * MacOS - + * Evergreen.app + * Contents + * Frameworks + * Resources + * MacOS +
Create an APP folder structure with the following commands:
Creating a folder structure - mkdir -p Evergreen.app/Contents/Frameworks - mkdir -p Evergreen.app/Contents/Resources - mkdir -p Evergreen.app/Contents/MacOS - + mkdir -p Evergreen.app/Contents/Frameworks + mkdir -p Evergreen.app/Contents/Resources + mkdir -p Evergreen.app/Contents/MacOS +
@@ -143,31 +151,31 @@
Creating a new file - <?xml version="1.0" encoding="UTF-8"?> - <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> - <plist version="1.0"> - <dict> - <key>CFBundleExecutable</key> - <string>xulrunner</string> - <key>CFBundleGetInfoString</key> - <string>OpenILS open_ils_staff_client rel_1_6_0_7</string> - <key>CFBundleInfoDictionaryVersion</key> - <string>6.0</string> - <key>CFBundleName</key> - <string>Evergreen Staff Client</string> - <key>CFBundlePackageType</key> - <string>APPL</string> - <key>CFBundleShortVersionString</key> - <string>rel_1_6_0_7</string> - <key>CFBundleVersion</key> - <string>rel_1_6_0_7.rel_1_6_0_7</string> - <key>NSAppleScriptEnabled</key> - <true/> - <key>CFBundleTypeIconFile</key> - <string>Evergreen.icns</string> - </dict> - </plist> - + <?xml version="1.0" encoding="UTF-8"?> + <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> + <plist version="1.0"> + <dict> + <key>CFBundleExecutable</key> + <string>xulrunner</string> + <key>CFBundleGetInfoString</key> + <string>OpenILS open_ils_staff_client rel_1_6_0_7</string> + <key>CFBundleInfoDictionaryVersion</key> + <string>6.0</string> + <key>CFBundleName</key> + <string>Evergreen Staff Client</string> + <key>CFBundlePackageType</key> + <string>APPL</string> + <key>CFBundleShortVersionString</key> + <string>rel_1_6_0_7</string> + <key>CFBundleVersion</key> + <string>rel_1_6_0_7.rel_1_6_0_7</string> + <key>NSAppleScriptEnabled</key> + <true/> + <key>CFBundleTypeIconFile</key> + <string>Evergreen.icns</string> + </dict> + </plist> +
Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (see above for recommendations). @@ -176,17 +184,17 @@
Example of APP file framework - * Evergreen.app/ - __* Contents/ - ____* Frameworks/ - ______* XUL.Framework/ - ______* Versions/ - ________* Current -> 1.9.1.3 (symlink) - ________* 1.9.1.3/ - ______* XUL -> Versions/Current/XUL - ______* libxpcom.dylib -> Versions/Current/libxpcom.dylib - ______* xulrunner-bin -> Versions/Current/xulrunner-bin - + * Evergreen.app/ + __* Contents/ + ____* Frameworks/ + ______* XUL.Framework/ + ______* Versions/ + ________* Current -> 1.9.1.3 (symlink) + ________* 1.9.1.3/ + ______* XUL -> Versions/Current/XUL + ______* libxpcom.dylib -> Versions/Current/libxpcom.dylib + ______* xulrunner-bin -> Versions/Current/xulrunner-bin +
Copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/MacOS (do not symlink; copy the file). @@ -195,23 +203,23 @@
Example APP file - * Evergreen.app/ - __* Contents/ - ____* Resources/ - ______* BUILD_ID - ______* application.ini - ______* chrome/ - ______* components/ - ______* etc. - + * Evergreen.app/ + __* Contents/ + ____* Resources/ + ______* BUILD_ID + ______* application.ini + ______* chrome/ + ______* components/ + ______* etc. +
Put a Mac format icon file named Evergreen.icns in Resources. - - +
+
Installing on Linux
Quick Upgrade of the Staff Client @@ -221,18 +229,18 @@
Copying the Staff Client to a remote workstation - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ scp -r build user@client.linux.machine:~/eg-client-x.x.x.x/ - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ scp -r build user@client.linux.machine:~/eg-client-x.x.x.x/ +
To test the newly copied Staff Client, as the opensrf user log into the remote workstation and execute it as shown:
Testing the copied Staff Client - $ su - opensrf - $ xulrunner ~/eg-client-x.x.x.x/build/application.ini - + $ su - opensrf + $ xulrunner ~/eg-client-x.x.x.x/build/application.ini +
@@ -244,10 +252,10 @@
Creating a symbolic link - $ su - root - $ cd /openils/var/web/xul - $ ln -s SERVER_BUILD_ID/ CLIENT_BUILD_ID - + $ su - root + $ cd /openils/var/web/xul + $ ln -s SERVER_BUILD_ID/ CLIENT_BUILD_ID +
@@ -260,9 +268,9 @@
Installing subversion and xulrunner - $ sudo apt-get install subversion - $ sudo apt-get install xulrunner - + $ sudo apt-get install subversion + $ sudo apt-get install xulrunner +
@@ -280,10 +288,10 @@
Downloading the source code - $ su - opensrf - $ cd /YOUR/DOWNLOAD/DIRECTORY - $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_2_1_4/ - + $ su - opensrf + $ cd /YOUR/DOWNLOAD/DIRECTORY + $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_2_1_4/ +
Remember to change "rel_1_2_1_4" to the appropriate tag for your installation. @@ -299,12 +307,12 @@
Finding the downloaded source code - $ su - opensrf - $ cd /YOUR/DOWNLOAD/DIRECTORY - $ cd Open-ILS/xul/staff_client - $ make STAFF_CLIENT_BUILD_ID='rel_1_2_1_4' - ... - + $ su - opensrf + $ cd /YOUR/DOWNLOAD/DIRECTORY + $ cd Open-ILS/xul/staff_client + $ make STAFF_CLIENT_BUILD_ID='rel_1_2_1_4' + ... +
@@ -329,14 +337,14 @@
Building from a "subversion" checkout - $ su - opensrf - $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_4_0_4/ - $ cd rel_1_4_0_4 - $ ./autogen.sh # If you downloaded a .tar.gz of Evergreen, you may skip this step - $ ./configure --prefix=/openils --sysconfdir=/openils/conf - $ cd Open-ILS/xul/staff_client/ - $ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install - + $ su - opensrf + $ svn co svn://svn.open-ils.org/ILS/tags/rel_1_4_0_4/ + $ cd rel_1_4_0_4 + $ ./autogen.sh # If you downloaded a .tar.gz of Evergreen, you may skip this step + $ ./configure --prefix=/openils --sysconfdir=/openils/conf + $ cd Open-ILS/xul/staff_client/ + $ make STAFF_CLIENT_BUILD_ID='rel_1_4_0_4' install +
@@ -347,9 +355,9 @@
Running the Staff Client - $ su - opensrf - $ xulrunner application.ini - + $ su - opensrf + $ xulrunner application.ini +
@@ -358,32 +366,32 @@
Creating a "staging" directory - $ mkdir ~/<Destination Directory> - $ cd ~/<Download Directory>/Open-ILS/xul/ - $ cp -r staff_client ~/<Destination Directory> - + $ mkdir ~/<Destination Directory> + $ cd ~/<Download Directory>/Open-ILS/xul/ + $ cp -r staff_client ~/<Destination Directory> +
Finally, test the Staff Client to verify that all the necessary files were moved to the destination directory:
Testing the copied Staff Client - $ cd ~/<Destination Directory>/staff_client/build - $ xulrunner application.ini - + $ cd ~/<Destination Directory>/staff_client/build + $ xulrunner application.ini +
If there were no problems, then finish the cleanup by removing the original download directory and all subdirectories:
Cleaning up - $ rm -r -f ~/<Download Directory> - + $ rm -r -f ~/<Download Directory> +
Finally, test the copied Staff Client. You can create "Desktop / Start Menu / K-Menu" shortcuts for the Staff Client by using the following command as the target:
Running the copied Staff Client - $ xulrunner ~/<Destination Directory>/staff_client/build/application.ini - + $ xulrunner ~/<Destination Directory>/staff_client/build/application.ini +
@@ -398,8 +406,8 @@
Installing "wine" - $ sudo apt-get install wine - + $ sudo apt-get install wine +
@@ -408,10 +416,10 @@
Downloading the Staff Client installer - $ su - opensrf - $ cd /YOUR/DOWNLOAD/DIRECTORY - $ wget http://open-ils.org/downloads/evergreen-setup-rel_version-number.exe - + $ su - opensrf + $ cd /YOUR/DOWNLOAD/DIRECTORY + $ wget http://open-ils.org/downloads/evergreen-setup-rel_version-number.exe +
@@ -420,10 +428,10 @@
Using Wine to run the Windows installer - $ su - opensrf - $ cd /YOUR/DOWNLOAD/DIRECTORY - $ wine evergreen-setup-rel_version-number.exe - + $ su - opensrf + $ cd /YOUR/DOWNLOAD/DIRECTORY + $ wine evergreen-setup-rel_version-number.exe +
If this step fails, you may need to configure Wine first to properly emulate Windows XP. To do so, type "winecfg" from the command line; in the "Applications" tab of the window that pops up, select "Default Settings" and choose "Windows XP" from the drop-down menu, then click "Apply". @@ -433,10 +441,6 @@
-
- Running the Staff Client over an SSH Tunnel - The Staff Client can use an SSH tunnel as a SOCKS 5 proxy. For more details, see the section . -
Assigning Workstation Names The Staff Client must be assigned to a library and given a unique name before it will connect fully to the Evergreen server. The only restriction is that the workstation's name must be unique within the assigned library. Make sure to select a workstation name that you will remember later, and reflects the role, purpose, and/or location of a particular computer. These names will come up later in statistical reporting, and can also be handy when troubleshooting. @@ -469,7 +473,7 @@ You are now ready to log into the Staff Client for the first time. Type in your password again, and hit Login.
- +
Manually Building the Staff Client @@ -484,22 +488,22 @@
Commands used during normal Evergreen build - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_7 install - ... - + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make STAFF_CLIENT_BUILD_ID=rel_1_6_0_7 install + ... +
The following commands will manually build the Staff Client using a different BUILD_ID. As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:
Commands to manually build the Staff Client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make STAFF_CLIENT_BUILD_ID=my_test_id build - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_BUILD_ID=my_test_id build + ... +
@@ -509,11 +513,11 @@
Commands used during normal Evergreen build - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make STAFF_CLIENT_VERSION=0mytest.200 install - ... - + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make STAFF_CLIENT_VERSION=0mytest.200 install + ... +
The following commands will manually build the Staff Client using a different VERSION. If you plan to make extensions update automatically, the VERSION needs to conform to the format recommended in Toolkit Version Format and newer versions need to be "higher" than older versions. @@ -521,11 +525,11 @@
Commands to manually build the Staff Client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make STAFF_CLIENT_VERSION=0mytest.200 build - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_VERSION=0mytest.200 build + ... +
@@ -535,11 +539,11 @@
Commands used during normal Evergreen build - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make STAFF_CLIENT_STAMP_ID=my_test_stamp install - ... - + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make STAFF_CLIENT_STAMP_ID=my_test_stamp install + ... +
The following commands will manually build the Staff Client using a different STAMP_ID. It is possible to have multiple versions of the Staff Client by specifying a different STAMP_ID for each, possibly for different uses or client-side customizations. @@ -547,11 +551,11 @@
Commands to manually build the Staff Client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make STAFF_CLIENT_STAMP_ID=my_test_stamp build - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make STAFF_CLIENT_STAMP_ID=my_test_stamp build + ... +
@@ -626,11 +630,11 @@
Commands to do a "developer build" - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make devbuild - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make devbuild + ... +
@@ -640,24 +644,24 @@
Commands to compress Javascript - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make compress-javascript - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make compress-javascript + ... +
You can also combine Javascript review and compression, and also perform a "developer build". As the opensrf user, run the following commands from the Staff Client source directory:
Commands to compress Javascript and do a "developer build" - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - - # order of options is important! - $ make devbuild compress-javascript - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + + # order of options is important! + $ make devbuild compress-javascript + ... +
@@ -666,22 +670,22 @@
Commands to set AUTOUPDATE_HOST for normal Evergreen build - $ su - root - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ make AUTOUPDATE_HOST=localhost install - ... - + $ su - root + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ make AUTOUPDATE_HOST=localhost install + ... +
You can manually set AUTOUPDATE_HOST to set up automatic update checking. The following commands will manually build the Staff Client using a different AUTOUPDATE_HOST. As the opensrf user, change directory to the Staff Client source directory, then set the variable and build the Staff Client:
Commands to manually specify AUTOUPDATE_HOST - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make AUTOUPDATE_HOST=localhost build - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make AUTOUPDATE_HOST=localhost build + ... +
For more information on Automatic Updates, see the section . @@ -694,11 +698,11 @@
Commands to install the Staff Client on the same machine - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ mkdir -p "/openils/var/web/xul/$(cat build/BUILD_ID)" - $ cp -R build/server "/openils/var/web/xul/$(cat build/BUILD_ID)" - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ mkdir -p "/openils/var/web/xul/$(cat build/BUILD_ID)" + $ cp -R build/server "/openils/var/web/xul/$(cat build/BUILD_ID)" +
@@ -712,11 +716,11 @@
Commands to package a "generic" client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make generic-client - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make generic-client + ... +
@@ -745,11 +749,11 @@
Commands to build a Windows client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make win-client - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make win-client + ... +
@@ -759,11 +763,11 @@
Commands to build a Linux client - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make linux-client - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make linux-client + ... +
@@ -773,11 +777,11 @@
Commands to build a Firefox extension - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make extension - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make extension + ... +
@@ -810,12 +814,12 @@
Commands to configure Evergreen - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 - $ ./configure --prefix=/openils --sysconfdir=/openils/conf --with-updateshost=hostname - $ make - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7 + $ ./configure --prefix=/openils --sysconfdir=/openils/conf --with-updateshost=hostname + $ make + ... +
@@ -833,23 +837,23 @@
Commands for building updates - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - - # command to build all updates at once: - $ make updates - ... - - # commands to build updates individually: - $ make generic-updates - ... - $ make win-updates - ... - $ make linux-updates - ... - $ make extension-updates - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + + # command to build all updates at once: + $ make updates + ... + + # commands to build updates individually: + $ make generic-updates + ... + $ make win-updates + ... + $ make linux-updates + ... + $ make extension-updates + ... +
@@ -858,23 +862,23 @@ The clients will be installed alongside the updates and listed on the "manualupdate.html" page, rather than left in the Staff Client directory. As the opensrf user, change directory to the Staff Client source directory, then execute the following commands:
- Commands for building updates + Commands for building updates with clients - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - - # command to build all updates at once: - $ make updates-client - ... - - # commands to build updates individually: - $ make generic-updates-client - ... - $ make win-updates-client - ... - $ make linux-updates-client - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + + # command to build all updates at once: + $ make updates-client + ... + + # commands to build updates individually: + $ make generic-updates-client + ... + $ make win-updates-client + ... + $ make linux-updates-client + ... +
@@ -886,10 +890,10 @@
Changing file permissions of scripts - $ su - root - $ cd /openils/var/updates/pub - $ chmod +x check download manualupdate.html update.rdf - + $ su - root + $ cd /openils/var/updates/pub + $ chmod +x check download manualupdate.html update.rdf +
@@ -904,11 +908,11 @@
Command to add start menu option - $ su - opensrf - $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client - $ make NSIS_EXTRAOPTS=-DPROFILES win-client - ... - + $ su - opensrf + $ cd /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client + $ make NSIS_EXTRAOPTS=-DPROFILES win-client + ... +
@@ -930,67 +934,69 @@ $ xulrunner /home/opensrf/Evergreen-ILS-1.6.0.7/Open-ILS/xul/staff_client/build/application.ini -
-
- Configuring a Proxy for the Staff Client - - Why Use a Proxy for the Staff Client? - There are several reasons for sending network traffic for the Staff Client through an SSH proxy: - - - Firewalls may prevent you from reaching the server. This may happen when you are connecting the Staff Client to a test server that should not be available generally, or it may be the result of network design priorities other than ease of use. - - - You may wish to improve security where Staff Client traffic may be susceptible to network eavesdropping. This is especially true when wireless is otherwise the best option for connecting a staff machine to the network. - - - - - Setting Up an SSH Tunnel - You will need a server that allows you to log in via SSH and has network access to the Evergreen server you want to reach. You will use your username and password for that SSH server to set up a tunnel. - For Windows users, one good solution is the open-source utility PuTTY, a free telnet/SSH client]]. When setting up a PuTTY session: -
- Setting up an SSH tunnel in PuTTY - - - - - -
- - Use the menu on the left to go to Connection > SSH > Tunnels. - Enter ''9999'' in the "Source port". - Choose "Dynamic". Do not enter anything in the Destination text entry box. - Click the "Add" button. "D9999" will now appear in the "Forwarded ports" list. - Use the menu on the left to go back to "Session", and enter the host name of the SSH server. - A window will open up so that you can enter your username and password. Once you are logged in, the tunnel is open. - - - - Configuring the Staff Client to Use the SSH Tunnel - In order to tell the Staff Client that all traffic should be sent through the SSH tunnel just configured, you must edit the file C:\Program Files\Evergreen Staff Client\greprefs\all.js. Search this file for the word socks to find the appropriate section for the following changes. -
- The SOCKS section of "all.js" before changes - - - - - -
- Make the following changes: - - Change the value of network.proxy.socks from "" to "localhost". - Change the value of network.proxy.socks_port from "0" to 9999. - -
- The SOCKS section of "all.js" after changes - - - - - -
- If everything is working correctly, you should now be able to run the Staff Client and all its data will be sent encrypted through the SSH tunnel you have just configured. + + Running the Staff Client over an SSH Tunnel + The Staff Client can use an SSH tunnel as a SOCKS 5 proxy. +
+ Configuring a Proxy for the Staff Client + There are several reasons for sending network traffic for the Staff Client through an SSH proxy: + + + Firewalls may prevent you from reaching the server. This may happen when you are connecting the Staff Client to a test server that should not be available generally, or it may be the result of network design priorities other than ease of use. + + + You may wish to improve security where Staff Client traffic may be susceptible to network eavesdropping. This is especially true when wireless is otherwise the best option for connecting a staff machine to the network. + + +
+
+ Setting Up an SSH Tunnel + You will need a server that allows you to log in via SSH and has network access to the Evergreen server you want to reach. You will use your username and password for that SSH server to set up a tunnel. + For Windows users, one good solution is the open-source utility PuTTY, a free telnet/SSH client]]. When setting up a PuTTY session: +
+ Setting up an SSH tunnel in PuTTY + + + + + +
+ + Use the menu on the left to go to Connection > SSH > Tunnels. + Enter ''9999'' in the "Source port". + Choose "Dynamic". Do not enter anything in the Destination text entry box. + Click the "Add" button. "D9999" will now appear in the "Forwarded ports" list. + Use the menu on the left to go back to "Session", and enter the host name of the SSH server. + A window will open up so that you can enter your username and password. Once you are logged in, the tunnel is open. + + See How to set up SSH (for the beginner) for information on setting up SSH for other client operating systems, +
+
+ Configuring the Staff Client to Use the SSH Tunnel + In order to tell the Staff Client that all traffic should be sent through the SSH tunnel just configured, you must edit the file C:\Program Files\Evergreen Staff Client\greprefs\all.js. Search this file for the word socks to find the appropriate section for the following changes. +
+ The SOCKS section of "all.js" before changes + + + + + +
+ Make the following changes: + + Change the value of network.proxy.socks from "" to "localhost". + Change the value of network.proxy.socks_port from "0" to 9999. + +
+ The SOCKS section of "all.js" after changes + + + + + +
+ If everything is working correctly, you should now be able to run the Staff Client and all its data will be sent encrypted through the SSH tunnel you have just configured. +
-- 2.11.0