User Tools

Site Tools


evergreen-user:installing_and_running_the_staff_client

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
evergreen-user:installing_and_running_the_staff_client [2010/05/20 11:00] aatreevergreen-user:installing_and_running_the_staff_client [2022/02/10 13:34] – external edit 127.0.0.1
Line 3: Line 3:
  
 ====== Installing and Running the Staff Client ====== ====== Installing and Running the Staff Client ======
 +NOTE: These instructions are also available in the Evergreen documentation at [[http://docs.evergreen-ils.org/1.6/draft/html/staffclientinstallation.html]]. In github: [[http://github.com/rsoulliere/Evergreen-DocBook/blob/master/1.6/admin/staffclientinstallation.xml]].
  
 ===== Installing On Windows ===== ===== Installing On Windows =====
Line 17: Line 17:
 {{:evergreen-user:staff-client_unconfigured.jpg|}} {{:evergreen-user:staff-client_unconfigured.jpg|}}
  
-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. \\ \\+First, configure the server you would like to connect to in the **Server** section. 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 every workstation is to assign it a workstation name. This is covered in the [[Workstation Names]] section of the documentation.  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 every workstation is to assign it a workstation name. This is covered in the [[Workstation Names]] section of the documentation. 
Line 125: Line 125:
  <key>CFBundleTypeIconFile</key>  <key>CFBundleTypeIconFile</key>
         <string>Evergreen.icns</string>         <string>Evergreen.icns</string>
 +        <key>CFBundleIdentifier</key>
 +        <string>org.evergreen-ils.Evergreen</string>
 </dict> </dict>
 </plist> </plist>
Line 141: Line 143:
             * libxpcom.dylib -> Versions/Current/libxpcom.dylib             * libxpcom.dylib -> Versions/Current/libxpcom.dylib
             * xulrunner-bin -> Versions/Current/xulrunner-bin             * xulrunner-bin -> Versions/Current/xulrunner-bin
-  - copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/MacOS (do not symlink, copy the file)+  - copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/Contents/MacOS (do not symlink, copy the file)
   - Make Evergreen.app/Resources the root of your Evergreen application files like this:   - Make Evergreen.app/Resources the root of your Evergreen application files like this:
     * Evergreen.app/     * Evergreen.app/
Line 152: Line 154:
           * etc.           * etc.
   - Put a Mac format icon file named Evergreen.icns in Resources    - Put a Mac format icon file named Evergreen.icns in Resources 
 +
 +==== WineBottler ====
 +
 +  - download and install WineBottler: [[http://winebottler.kronenberg.org/|http://winebottler.kronenberg.org/]]
 +  - open the application "WineBottler"
 +  - select "Create Custom Prefixes"
 +  - select the desired windows installer as your "Install File"
 +  - set the "Runtime arguments" to "build/application.ini"
 +  - click "Install" -- you will now see the Evergreen Windows Installer
 +  - when you get to the end **UNCHECK** the option to "run Evergreen now" and complete the installation
 +  - WineBottler should then pop up a dialog for you to select an executable -- select xulrunner.exe
 +
  
 ===== Installing On Linux ===== ===== Installing On Linux =====
Line 204: Line 218:
 Next, you'll need to determine which //tag// to use when downloading the source code.  Tags are markers in the source code to create a snapshot of the code as it existed at a certain time; tags usually point to tested and stable code, or at least a community-recognized release version.  Next, you'll need to determine which //tag// to use when downloading the source code.  Tags are markers in the source code to create a snapshot of the code as it existed at a certain time; tags usually point to tested and stable code, or at least a community-recognized release version. 
  
-To determine which tag to use, browse to http://svn.open-ils.org/trac/ILS Look in the "Visit" drop-down box.  You will see a list of Branches and, further down, a list of Tags.  You'll have to do some guessworkbut it's fairly straightforward to determine which tag to use.  If the server is on version 1.2.1.4you'll want to use the tag that looks most appropriate.  As you look through the tag list, you'll notice a tag named 'rel_1_2_1_4' This is the tag you'll want to use; make a note of it, because you'll need the tag name for the next step +To determine which tag to use, browse to http://git.evergreen-ils.org/?p=Evergreen.git;a=summary.  The summary page includes a list of tags and branches.  Depending on whether a release was made before or after the project moved to Gitselect either the Git tag or the branch converted from an SVN release tag (e.g., tags/rel_1_2_1_4.
  
 ==2b: Download the Source Code.== ==2b: Download the Source Code.==
 +
 Now, open a terminal (command-line prompt) and navigate to the directory in which you wish to download the staff client.  Navigate to the desired directory and use the following command to download the proper version of the source code by tag: Now, open a terminal (command-line prompt) and navigate to the directory in which you wish to download the staff client.  Navigate to the desired directory and use the following command to download the proper version of the source code by tag:
 <code> <code>
-svn co svn://svn.open-ils.org/ILS/tags/rel_1_2_1_4/+git clone git://git.evergreen-ils.org/Evergreen.git 
 +git checkout -b tmp_branch origin/rel_1_2_1 # or git checkout rel_1_2_1
 </code> </code>
 Note that you'll want to change "rel_1_2_1_4" to the appropriate tag for your installation. Note that you'll want to change "rel_1_2_1_4" to the appropriate tag for your installation.
Line 240: Line 255:
  
 <code> <code>
-svn co svn://svn.open-ils.org/ILS/tags/rel_1_4_0_4/ +git clone git://git.evergreen-ils.org/Evergreen.git 
-cd rel_1_4_0_4+git checkout rel_1_4_0_4
 ./autogen.sh   # If you downloaded a .tar.gz of Evergreen, you may skip this step ./autogen.sh   # If you downloaded a .tar.gz of Evergreen, you may skip this step
 ./configure --prefix=/openils --sysconfdir=/openils/conf ./configure --prefix=/openils --sysconfdir=/openils/conf
Line 305: Line 320:
  
 The Evergreen Staff Client can use an SSH tunnel as a SOCKS 5 proxy.  For more details, see [[evergreen-user:configuring_a_proxy_for_the_staff_client]]. The Evergreen Staff Client can use an SSH tunnel as a SOCKS 5 proxy.  For more details, see [[evergreen-user:configuring_a_proxy_for_the_staff_client]].
- 

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.