Changes between Version 10 and Version 11 of doc/install/advanced

Timestamp:

Sep 10, 2018 8:17:41 AM (7 years ago)

Author:

raasch

Comment:

--

doc/install/advanced

@@ -149 +149 @@
 
 
-== [=#update]Installation of new / other revisions, revision update =
+== [=#update]Installation of new / other revisions, revision update ==
 
 All code revisions are documented under [wiki:doc/tec/changelog]. The PALM group announces major code revisions via the PALM mailing list. You will be automatically set on the list by creating an account using the [[//trac/register|register form]].\\\\
@@ -184 +184 @@
 because otherwise the {{{make}}} mechanism will not detect any source file that needs to be compiled. As an alternative, instead of ''touching'' the files, you may delete the {{{MAKE_DEPOSITORY}}} folder before calling {{{palmbuild}}}, but then the complete code will be re-compiled.  
 
-As a last step, a suitable test run should be carried out. It should be carefully examined whether and how the results created by the new revision differ from those of the old version. Possible discrepancies which go beyond the ones announced in the [wiki:doc/tec/changelog PALM change log] should be communicated as soon as possible via our [/newticket ticket system].
+As a last step, a suitable test run should be carried out. It should be carefully examined whether and how the results created by the new revision differ from those of the old version. Possible discrepancies which go beyond the ones announced in the [wiki:doc/tec/changelog PALM change log] should be communicated as soon as possible via our [/newticket ticket system].\\\\
+
+
+== [=#multiple]Central installation for multiple users ==
+
+For a working group with multiple users, who only apply the PALM code and have no need to modify the working copy of the repository, PALM needs to be installed only once. The system administrator (or any other person) has to do the installation as described above. Assuming that the working copy of the repository (folder {{{trunk}}}) is in folder {{{/path_to_the_central_installation}}}, and that a configuration file {{{.palm.config.default}}} has been created in that folder, each single user has to create his/her own working directory:
+{{{
+   mkdir  $HOME/palm/current_version/JOBS
+   cd  $HOME/palm/current_version
+   cp  /path_to_the_central_installation/.palm.config.default  .
+}}}
+Then edit the copied configuration file and modify folder paths as follows:
+{{{
+%base_directory    /path_to_the_central_installation
+%source_path       /path_to_the_central_installation/trunk/SOURCE
+%base_data         ~/palm/current_version/JOBS
+%user_source_path  $HOME/palm/current_version/JOBS/$jobname/USER_CODE
+%local_username    <replace with your username>
+%fast_io_catalog   <replace with your fast file system folder>
+}}}
+Every user will then use the pre-compiled version of PALM that has been created for the central installation under the configuration identifier {{{default}}}. {{{palmrun}}} can only be called with this configuration identifier ({{{palmrun -h default ....}}}). If other configurations are required, they have to be created ''by the administrator'' under the central installation
+{{{
+   cp  /path_to_the_central_installation/trunk/SCRIPTS/.palm.config.default  /path_to_the_central_installation/.palm.config.config_new
+   # edit .palm.config.config_new
+   cd /path_to_the_central_installation
+   palmbuild  -h config_new
+}}}
+After that, users need to copy and modify this configuration file as described above, and can use this configuration via {{{palmrun -h config_new ....}}}.