Changes between Version 2 and Version 3 of UnixProjectPackage


Ignore:
Timestamp:
Jul 3, 2008, 6:01:59 AM (16 years ago)
Author:
Eric Myers
Comment:

How do we do monospace on this wiki?; See Also

Legend:

Unmodified
Added
Removed
Modified
  • UnixProjectPackage

    v2 v3  
    44The purpose of this page is to describe what is needed to create a Unix package to install the BOINC software needed to create and run a BOINC project.  The primary idea is to make it easy for anyone who is interested in doing so to install the package, run some initializations scripts, and thus easily create a working BOINC project.
    55
    6 This will necessarily involve sorting through all the items listed on the ProjectMain page, and the steps described in the ServerIntro page, to see what can be automated, and what still needs to be done by the project admin "by
     6This will necessarily involve sorting through all the items listed on the ProjectMain page, and the steps described in the ServerIntro page, to see what can be automated, and what still needs to be done by the project admin "by hand"
    77
    88A BOINC project must be hosted on a Unix computer, but any Unix/Linux distribution should be supported.  It will be useful to have different Linux distros use the same packaging principles and file locations to the extent that this is possible.  Files and directories should be placed in accordance with the guiding principles of the Filesystem Hierarchy Standard, which may be found at http://www.pathname.com/fhs/pub/fhs-2.3.html.   
    99
    10 Keep in mind that it is a requirement of rpm packages (and probably Debian as well?) that packages install without any user input or dialogue.   The package only installs the software.  It is then up to the user who creates the project to run <tt>make_project</tt> (or a script which wraps it?) to set up the project. 
     10Keep in mind that it is a requirement of rpm packages (and probably Debian as well?) that packages install without any user input or dialogue.   The package only installs the software.  It is then up to the user who creates the project to run {{{make_project}}} (or a script which wraps it?) to set up the project. 
    1111
    1212
     
    2020Keep in mind that we want to allow for the possibility of more than one project being hosted on the same server.
    2121
    22 The package should probably create a "boincadm" user and group.   Then there is a "projects" directory under the home directory of that user.  Then <tt>make_project</tt> simply creates the new project under that, as is the default.
     22The package should probably create a "boincadm" user and group.   Then there is a "projects" directory under the home directory of that user.  Then {{{make_project}}} simply creates the new project under that, as is the default.
    2323
    2424
    2525== Project Initiation ==
    2626
    27 Is it sufficient to run <tt>make_project</tt> from "boincadm", or is there anything else required first?
     27Is it sufficient to run {{{make_project}}} from "boincadm", or is there anything else required first?
    2828
    2929
     
    3434What files need to be provided, as templates which the project admin can then edit for their purpose (or which can be initially edited by an installation script)?
    3535   * Web server configuration file
     36   * config.xml
     37   * cron task to run {{{start --cron}}} script
    3638   * Log rotation config file?
     39   
    3740
    3841
    3942
     43== See Also ==
     44   * ServerIntro
     45   * ProjectMain
     46   * http://www.spy-hill.net/~myers/help/boinc/Create_Project.html
     47