Re: ISPMan Handbook - First Draft

> Hi Wil,
>
> I am all for having the POD documentation about the usage.
>
> The documentation I propose is a step by step guide on using the CLI.
>
> Example:
>
> Install ISPMan
> Add a reseller
> Add a client under the reseller
> Add a domain
> Set the client and reseller for the domain
> List domains
> Add a user in the domain
> Add a website in the domain
> List users/websites for the domain
>
> Manipulate DNS information for the domain
> Manipulate site-wide DNS information (very undocumented and powerful
> feature)
>
> etc
>
> best regards

OK Atif et al,

I've posted a first draft of a CLI document. I need help on 3 points, all
of which are indentified by ?? in the doc.

1) Is there a way to set "Extra Configuration" options for a vhost from
the command line? For instance a Redirect Rule, or aliasing a directory?
Do you have to hack ispman.addvhost each time, or just use the web
interface?

2) Is there a way to add secondary and/or nodns domains from the
commandline without hacking ispman.addDomain?

If I understand correctly:
  ispman.addSlaveDomain adds a Slave/Replica domain.
  ispman.addDomain adds a Primary Domain by default. With hacking it can
do any domain type.

3) How does the ispman.dnsset work with SOA records? Under my tests, the
script happy accepted my input but didn't actually change anything,
including LDAP. (Cross posted to ispman-developers).

Any preference on the Documentation License we use? Can I just start
sticking this stuff up on www.ispman.org?

http://www.azxws.com/ispman/


Tony Wasson





-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn