PHP-based installer

[ChristianB]

here is what I got working so far:
- Check requirements and file permissions to create conf/jarifa.conf
- Check the DB connection and create the tables
- Enter the root user with a random password (8 chars)
- Store the configuration into conf/jarifa.conf
- fail gracefully and inform the user about the mistake in all cases

The last thing is the account manager information in jarif.conf
<account_manager>
<name>Jarifa Server</name>
<logo>img/logo.png</logo>
<master_url>http://localhost/jarifa</master_url>
<min_passwd_length>1</min_passwd_length>
<usernames>1</usernames>
<repeat_sec>280</repeat_sec>
<public_signature>PUT SIGNATURE HERE</public_signature>
<boinc_user_email>em...@yourdomain.com</boinc_user_email>
<boinc_user_name>boinc_user</boinc_user_name>
<boinc_passwd>boinc_pass</boinc_passwd>
</account_manager>

Providing a form is easy but what criteria should I implement to check
the values? And how is the public_signature generated (this should
also be documented)? What is boinc_user_email and boinc_user_name used
for?

Regards
Christian

[Daniel Lombraña González]

Hi,

On Sun, Nov 30, 2008 at 1:35 PM, ChristianB <open.sou...@googlemail.com> wrote:

here is what I got working so far:
- Check requirements and file permissions to create conf/jarifa.conf
- Check the DB connection and create the tables
- Enter the root user with a random password (8 chars)
- Store the configuration into conf/jarifa.conf
- fail gracefully and inform the user about the mistake in all cases

Sounds great. Good work.
 

The last thing is the account manager information in jarif.conf
<account_manager>
   <name>Jarifa Server</name>
   <logo>img/logo.png</logo>
   <master_url>http://localhost/jarifa</master_url>
   <min_passwd_length>1</min_passwd_length>
   <usernames>1</usernames>
   <repeat_sec>280</repeat_sec>
   <public_signature>PUT SIGNATURE HERE</public_signature>
   <boinc_user_email>em...@yourdomain.com</boinc_user_email>
   <boinc_user_name>boinc_user</boinc_user_name>
   <boinc_passwd>boinc_pass</boinc_passwd>
</account_manager>

We have to create the config.xml file, to support the <min_core_client> item. It should be very easy to add the file.

Providing a form is easy but what criteria should I implement to check
the values? And how is the public_signature generated (this should
also be documented)? What is boinc_user_email and boinc_user_name used
for?

The public signature is created using the standard BOINC crypt_prog. I think it is documented here: http://jarifa.unex.es/wiki/wiki/Quickstart

boinc_user_email and boinc_user_name, are the items used for creating and joining BOINC projects. Jarifa used those items to, first, create the account on the given BOINC project if it not exists, and second, to attach a new computer to that project.

About the criteria for checking the values. You can add simple rules, like for example: strings no longer than 255 chars for <name>. Think in possible wrong values, and try to avoid them :)

Regards,

Daniel
 

Regards
Christian

--
··························································································································································
PhD Candidate
Cátedra Ceta-Ciemat de la Universidad de Extremadura
http://gea.unex.es/catedra-ceta-ciemat/
Universidad de Extremadura
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································