[Debian Wiki] Update of "BOINC/ServerGuide" by SteffenMoeller

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "BOINC/ServerGuide" page has been changed by SteffenMoeller:
http://wiki.debian.org/BOINC/ServerGuide?action=diff&rev1=77&rev2=78

Comment:
Integration of Dhananjay's description into the ServerGuide

  
  This section is currently been brought to some better shape at [[BOINC/ServerGuide/AppDeployment]].
  
- == Add your own application ==
- 
- The only thing that counts to have is the application that helps your very personal task at hand. This will be addressed in the upcoming section. The section at hand will take one of the example projects.
- 
- ||<style="background-color: red; width: 50%; vertical-align:top">Previously||<style="background-color: lightgreen; width: 50%; vertical-align:top;">Now||
- ||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperOld)>>||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperNew)>>||
- ||[[BOINC/ServerGuide/Include/PreparationWrapperOld|source]]||[[BOINC/ServerGuide/Include/PreparationWrapperNew|source]]||
- 
- 
  == Start BOINC demons ==
  
  Now its time to start the project, assuming we are still inside the project root,
@@ -330, +321 @@

  $ cat upload/ba/test_0_0 
  TEST STRING
  }}}
+ 
+ 
+ == Add your own application ==
+ 
+ The only thing that counts to have is the application that helps your very personal task at hand. There are two ways to achieve that:
+  i. a newly designed or modified app that knows how to speak the BOINC API
+  i. a wrapper to execute the working application through the regular UNIX command line
+ 
+ The creation of native BOINC-speaking applications is nothing a distribution can help much with, except for providing the boinc-dev package. Please raise your hand if you are inclined to prepare a similar tutorial for that. We continue with using the wrapper to bring your (or someone else's) legacy applications to BOINC:
+ 
+ === Preparations for using the wrapper for legacy (read: regular) applications ===
+ 
+ ||<style="background-color: red; width: 50%; vertical-align:top">Previously||<style="background-color: lightgreen; width: 50%; vertical-align:top;">Now||
+ ||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperOld)>>||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperNew)>>||
+ ||[[BOINC/ServerGuide/Include/PreparationWrapperOld|source]]||[[BOINC/ServerGuide/Include/PreparationWrapperNew|source]]||
+ 
+ === Getting the wrapper and binaries into your server's setup ===
+ 
+ Please follow [[BOINC/ServerGuide/WrapperApp]] for detailed instructions on how to get your application wrapped.
  
  = Management of your own project =
  
@@ -362, +372 @@

  and execute the commands using the standard variables.
  
  
+ === Disclaimer ===
  
- 
- This section still needs to be written. Frankly, we don't know, yet. To clarify
+ This section is not yet complete. While the instructions on how to get your
+ project up is basically fine, if extendable, there are a few issues that 
+ frankly we don't know how to solve exactly, yet, i.e.:
   * updates of the project pages
    * the web pages are most likely straight forward to bring to a new version
    * the database needs the schema to be adjusted ... how?
+  * integration with Debian infrastructure
-  * what clients are built through the Debian build daemons and which are not?
+   * what clients are built through the Debian build daemons and which are not?
-  * ...?
+   * shall there be static applications only or do we also allow dynamically linking ones?
+   * shall there be additional tests be performed by the client to report on issues prior to the distribution of work? Say checking the output of ldd?
+  * cross-platform compatibility with MacOS and Windows
+   * virtualisation is obvious and
+    * may be preferred by many, needs to be prepared, though
+    * GPU computing may not be supported that route
+   * support for cross-platform wrapper
+  * ... what is there that we are not even aware of, yet ...?
  
  = Why to use (or not to use) the Debian BOINC server maker package =