was [Re: [OGo-Developer]] install script modifications and additions suggestions/comments

Kelley G wrote:

>> Basically it should check for the following;
>>
>> -postgresql is installed or not (done)
> 
> 
> package manager does, this... do you mean a more explicit series of steps?

nope. just meet your requirements.

>> -if an ogo (OGo) database has been loaded,
> 
> 
>> -if the user want to overwrite this db or not
>> -then load the db
>> -if no db is present, recommend that the db be loaded with default 
>> name ogo (OGo...see why we need to deal with this..:))
> 
> 
> yes i prefer ogo, lower --  not caps
> 
>> -allow user over ride on db name as mutliple db's are required for some.
> 
> 
> this could be trouble... maybe a switch for admins who downbload. i 
> forsee newbie issues..

Not with the appropriate warning prompts and steps. ie:

Standard warning optional via a switch -W that is can be turned off at 
installation time. -w

eg:

**Warning: You are about to install or update the postgresql database. 
Make sure that you have reviewed the howto notes at http://## prior to 
proceeding. Please indicate your options:

1 yes I have read the notes and want to proceed.
2. no I have not read the notes and want to complete the postgresql load 
at a later time.
---------------------------------------------------------

IF the user selects (1) the script proceeds. If the user selects (2) the 
script terminates.
---------------------------------------------------------

If (1) then the script can have two options.
- option 1 below if no db detected.
- option 2 belwo is a db is detected
These should not be associated with a switch at start
----------------------------------------------------------

Continuing on with (1) if selected then the script can prompt the user 
with the following once it examines the postgresql setup.

(Option 1)
No previouse db was detected. Please select your option:

1. load default
2. load constraints default
3. load cyrus default
4. load update schema for older installations.

alternatively

(Option 2)
The installer had detected a previouse ogo db that is typically not 
overwritten. Please select your option.[1,2,3,4,....]

(1) I know what Im doing: overwrite exiting db with default name
(2) I know what Im doing: overwrite and allow me to rename the db: 
*dangeroue move bucko"
(3) do nothing and continue with installation

if (2) enter new db name: _____________________________
then script completes the pg setup and moves on to mext step.

If may be wise to have the script setup to announce completion of each 
reauested step and allow for a switch at start to override this. -PR 
(prompts) -pr In this manner the user can step through each component of 
the install and verify its completeness, or alternatively and 
preferrable learn what is going on.

eg:

rpm download complete, shall we continue with installation? y/n
rpm installation complete, shall we continue with postgresql setup y/m
postgresql installation complete, shall we continue with apache setup y/n
please select your OS
1. Redhat ver ......
2. SuSE ver.....
3. Debian vers.....
4. whatever...:)

OK we see that you have a SuSE 9.1 install. shall we proceed with apache 
  setup y/n
apache installation is complete. shall we continue with boot system 
integration y/n
We rember that you are on SuSE 9.1 Is this correct. y/n
OK..installation complete.
Restarting all required applications.
Done
Please logon to http://localhost//OpenGroupware.org as root with no 
passward and then set the password by access preferences. Your password 
will be activated upon logut.
Thanks for using OpenGroupware.org
Comments and suggestions to http://#
Enjoy.

Now the entire process is in nice "compartments" that can be stopped at 
any time for review. This can of course be avoided with an appropriate 
witch that provicdes for no prompts and a complete unattended install.

Could work.

>>
>> Fantasy request:
>>
>> -have the script check the version of the OS.
> 
> 
> already does a simple check, should be easy to extend, (with some 
> commmunity help)
> 
>> -check if ngowebmodule requirements are met

just identify what you need pls.


> this is what i'm working on currently.
> 
>> -install requirements via rpm, dpkg or whatever
> 
> 
> not clear on this statement
> 
>> -then lauch distro dependant build script for the module
> 
> 
> not clear on this.
> 
>>
>> The alternative and probably easier is if the script were to detect 
>> the version of OS and go home (to an archeive we can setup) and 
>> download the appropriate (build and tested) module. As distro's are on 
>> a 3 peryear release cylce for the majors, dedian updates very slowly 
>> and the commercial versions are now running at 2-3 year terms this is 
>> not a lot of work to maintain. Setting up a repository is also not 
>> much effort.

this is probably the simpler route to go. a wget call to an archive 
where we store updated and maintainded builds of the module per distro 
version.

Some will want to compile themselves. Instructions should suffice if the 
module is downloadable. Me thinks providing an autobuild system that 
detects and configures for all supported distro's may be a bit much of a 
  task?

>> If you can deal with the postgresql and apache parts in such a manner 
>> that it makes the install seamless per distro flavour that would be a 
>> tremendouse effort and contrib.
> 
> 
> yes this is number one priority.
> 
>>
>> Finally setting up the boot sequence as it distro dependent should in 
>> theory also not be that difficult. For suse for example it would be as 
>> simple as coping the init scripts to /etc/init.d via sudo or whatever 
>> and then running insserv. Probably works on rh based distro's as well. 
>> Again, as you have already included or are working on OS recognition 
>> for the script this final stap should not be overly 'expensive'.
> 
> 
> this would require some community input, but not difficult.

OK just let the list know what you need then...

>> The next task will be to build some sort of admin tool for OGo. Lots 
>> of ideas on that, however IANAD..:) Sorry.
> 
> 
> maybe move this large topic to discuss... :)



done..:)

/ch



-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss