Re: ispman-HEAD tasks cleanup

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like great changes to me.

I'm quite new to ispman. I've only been using it for a few months. The  
one major change I've made to my installation revolves around using  
cyrus virtual domains. With this setup, the uid is the same as their  
email address. The changes were not difficult to implement -- most of  
the changes were to ldap templates, control panel, and the creation of  
user directories. If people are interested, I do not believe it would  
be difficult to implement this feature in a way which would be  
compatible with the old model.

There are a couple other ideas I have been thinking of lately as well.  
I have been contemplating setting up a box that uses DAV instead of FTP  
for file transfers. Has anyone done this with ispman? I don't think it  
would be too hard to implement:
1. Change admin interface to allow for ftp, dav or none
2. Change directory permissions
3. Change webserver templates

I'm also running both apache 1.3 and 2.0 boxes. I'm only using ispman  
with the 2.0 boxes now because they require a different module for ldap  
authentication. It would be great if ispman could handle a mixed  
environment (or maybe it can and I'm just to thick to figure it out).

Cheers,
Paul

On Dec 30, 2004, at 9:25 AM, Atif Ghaffar wrote:

> Hi all,
>
> Short summary,
>
> After some time, I have got the chance to work again on ISPMan.
> I am helping Joerg to do the cleanup so the code is easier and the  
> logic is not everywhere.
>
> 2 main changes I did recently are.
>
> 1. params are passed by name to processes.
>    Until now we were passing a comma separated list of items and the  
> recieving function knew how to process it. This starts to get ugly...  
> so we change to name=value&name=value style as in GET URLs.
> For example: here are the params passed to process createHomeDirectory
> uid=xx_test_com&homeDirectory=/ispman/domains/test.com/users/ 
> xx_test_com&uidNumber=2279&gidNumber=2235
>
> This way the function can recieve the parameters as a hashref and  
> things get easier....
>
> 2. All the processes were defined in ispman-agent. This started to get  
> hairy too, there was pieces of logic every where.
> Now we have removed all the processing functions from ispman agent and  
> put them in a task directory.
>
> In this directory you will find tasks that ISPMan writes to the  
> processtable. These tasks have almost no logic. They are just like a  
> batch script.
>
> The task execute one or more commands with parameters. The commands  
> can be system commands such as rm, cp etc or ispman.* commands.
>
> It gets easier to understand what happens behind a task.
>
> please let me know your comments.
>
> best regards
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Ispman-developers mailing list
> Ispman-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/ispman-developers
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFB2xNQ4vygjarL2QkRAnbgAJ4mHUtOa/ErGPZZ/8Ugd6EwlD4HMQCgmbjG
nrEeKtJRXDsej0WVnQ5Mlu8=
=n8U3
-----END PGP SIGNATURE-----



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt