Menu
▾
▴
ispman-docs
|
From: Tony W. <wa...@az...> - 2004-01-28 16:25:14
|
Pheew! It's been almost a month since starting on the ISPMan Handbook, so I'm giving an update. I've posted a First Draft of the ISPMan Handbook in PDF, HTML and OpenOffice format. It is about 30 pages long. http://www.azxws.com/ispman/ Please let me know if you have suggestions or can expand one of the chapters. Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've also added a section about Migration, with some general tips. This needs to be expanded, since I've only done 2 migrations. Tony Wasson |
|
From: Wil C. <wc...@na...> - 2004-01-28 17:28:23
|
On Wed, 2004-01-28 at 08:25, Tony Wasson wrote: > Pheew! It's been almost a month since starting on the ISPMan Handbook, so > I'm giving an update. I've posted a First Draft of the ISPMan Handbook in > PDF, HTML and OpenOffice format. It is about 30 pages long. >=20 > http://www.azxws.com/ispman/ >=20 > Please let me know if you have suggestions or can expand one of the chapt= ers. Did you use OOo to generate the HTML and PDF? Could OOo generate links from the TOC to the contents? The images seem to be artificially scaled down, which makes the text on them illegible. Under "Filesystem Layout", /ispman/domains, there are example user directories of example.com/users/atif_domain_com example.com/users/arno_domain_com Which should be example.com/users/atif_example_com example.com/users/arno_example_com Exactly what "processes" are and why they're necessary does not seem to be explained (at least, not in the "Processes" section). The ldapvirtual stuff works for Postfix 1.1 also, if compiled for it. I also set up Postfix to use an LDAP map for 'relay_domains' (the only big difference is the query_filter and result_attribute): http://nakedape.cc/wiki/index.cgi/IspManPostfixRelay I think you've got the headings for the "PureFTPd" and "ProFTPd" sections backwards. The first two images in chapter 5 are missing in the on-line version: missing "1. Click on Add Domain, filling out these pieces of info:" and "2. The next screen looks like this". > Chapter 1 is wrapping up, and the rest of it beginning to take shape. I'v= e > also added a section about Migration, with some general tips. This needs > to be expanded, since I've only done 2 migrations. One thing I've recently done for migration (the only one I've done so far) is to modify the migration tool from PADL to generate the entries I wanted. 'uid' seems to work okay as a multi-valued attribute, and to avoid the trouble of figuring out all the right filters, I just created entries with both 'username' and 'username_example_com'. Wil --=20 Wil Cooley wc...@na... Naked Ape Consulting http://nakedape.cc * * * * * * * Good, fast and cheap: Pick all 3! * * * * * * * * Naked Ape Consulting http://nakedape.cc/r/sg * * SnapGear Linux Firewall/VPN Appliances Reseller * |
|
From: Wim K. <wi...@ny...> - 2004-01-28 18:13:11
|
Wil Cooley wrote: >On Wed, 2004-01-28 at 08:25, Tony Wasson wrote: > > >>Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've >>also added a section about Migration, with some general tips. This needs >>to be expanded, since I've only done 2 migrations. >> >> > >One thing I've recently done for migration (the only one I've done so >far) is to modify the migration tool from PADL to generate the entries I >wanted. 'uid' seems to work okay as a multi-valued attribute, and to >avoid the trouble of figuring out all the right filters, I just created >entries with both 'username' and 'username_example_com'. > > I did this as well... all our users have 3 uids: username, username_example_com, and use...@ex.... This is because the "old" server had the users from all domains using the same servername (not mail.theirdomain.com) for POP/IMAP/SMTP with the short Unix username. Once the migration is done, we'll probably send them an email to change their settings. After a grace period we can drop the extra UIDs so that we can have jd...@do... as a a totally seperate entity from jd...@do.... Wim |
|
From: Tony W. <wa...@az...> - 2004-01-28 18:06:53
|
> On Wed, 2004-01-28 at 08:25, Tony Wasson wrote: >> Pheew! It's been almost a month since starting on the ISPMan Handbook, >> so >> I'm giving an update. I've posted a First Draft of the ISPMan Handbook >> in >> PDF, HTML and OpenOffice format. It is about 30 pages long. >> >> http://www.azxws.com/ispman/ >> >> Please let me know if you have suggestions or can expand one of the >> chapters. > > Did you use OOo to generate the HTML and PDF? Could OOo generate links > from the TOC to the contents? Yes, I just did "Export to PDF" and "Save as > HTML". If I knew a little more about OO I could probably make the links work. > The images seem to be artificially scaled down, which makes the text on > them illegible. OK, I will see what I can do. > Under "Filesystem Layout", /ispman/domains, there are example user > directories of > > example.com/users/atif_domain_com > > example.com/users/arno_domain_com > > Which should be > > example.com/users/atif_example_com > > example.com/users/arno_example_com Ooops. I was debating switching ALL the examples to "domain.tld" > Exactly what "processes" are and why they're necessary does not seem to > be explained (at least, not in the "Processes" section). You're right, I need to fill this out more. > The ldapvirtual stuff works for Postfix 1.1 also, if compiled for it. I > also set up Postfix to use an LDAP map for 'relay_domains' (the only big > difference is the query_filter and result_attribute): > > http://nakedape.cc/wiki/index.cgi/IspManPostfixRelay > > I think you've got the headings for the "PureFTPd" and "ProFTPd" > sections backwards. > > The first two images in chapter 5 are missing in the on-line version: > missing "1. Click on Add Domain, filling out these pieces of info:" and > "2. The next screen looks like this". > >> Chapter 1 is wrapping up, and the rest of it beginning to take shape. >> I've >> also added a section about Migration, with some general tips. This needs >> to be expanded, since I've only done 2 migrations. > > One thing I've recently done for migration (the only one I've done so > far) is to modify the migration tool from PADL to generate the entries I > wanted. 'uid' seems to work okay as a multi-valued attribute, and to > avoid the trouble of figuring out all the right filters, I just created > entries with both 'username' and 'username_example_com'. Interesting! I wanted to include several filter examples because I feel like everyone is "re-inventing" the wheel. Thanks for all the suggestions Wil. I will try to get these all done when I come back from vacation next week. In the mean time, feel free to hack on the documentation wherever you see fit and if you have time. I'd like this to be a community document. Tony Wasson |
|
From: Wil C. <wc...@na...> - 2004-01-28 18:14:47
|
On Wed, 2004-01-28 at 10:06, Tony Wasson wrote: > Ooops. I was debating switching ALL the examples to "domain.tld" 'example.com' is the recommended domain; they're reserved by RFC for documentation. ... > Interesting! I wanted to include several filter examples because I feel > like everyone is "re-inventing" the wheel. >=20 > Thanks for all the suggestions Wil. I will try to get these all done when > I come back from vacation next week. In the mean time, feel free to hack > on the documentation wherever you see fit and if you have time. I'd like > this to be a community document. Is it in CVS (I guess it doesn't matter)? Partly I'm concerned because I'm still only running 0.9.7+CVS in production, so I'm afraid I might not be entirely current. Wil --=20 Wil Cooley wc...@na... Naked Ape Consulting http://nakedape.cc * * * * * * Linux Services for Small Businesses * * * * * * * Naked Ape Consulting http://nakedape.cc * * Naked Ape Business Server http://nakedape.cc/r/smb * * Easy, reliable solutions for small businesses * |
|
From: Jeff M. <jm...@qn...> - 2004-01-29 09:38:09
|
Looks good, from what i've read so far. I will start looking for areas to contribute to shortly. Meanwhile, I made up a simple freebsd 4.9 install guide, of which I'd like some feedback from the community. I tried to write it in a casual narrative style, so the process is comfortable from start to finish. Its laid out to provide a pretty comprehensive tutorial for installation on FreeBSD, it's not limited to 4.9 but I've yet to test it with anything newer. I also included a number of beginners notes on the layout of ISPman, and some troubleshooting advice where possible. I haven't gone through it thoroughly to make sure everything is 100% accurate, but I took all the information directly from the test servers ive been working with so hopefully its pretty close. I plan to do some finishing cleanup and testing in the future. It's at http://www.meden.org/ispman-fbsd.htm Jeff Meden Tony Wasson wrote: >Pheew! It's been almost a month since starting on the ISPMan Handbook, so >I'm giving an update. I've posted a First Draft of the ISPMan Handbook in >PDF, HTML and OpenOffice format. It is about 30 pages long. > >http://www.azxws.com/ispman/ > >Please let me know if you have suggestions or can expand one of the chapters. > >Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've >also added a section about Migration, with some general tips. This needs >to be expanded, since I've only done 2 migrations. > >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 >_______________________________________________ >Ispman-docs mailing list >Isp...@li... >https://lists.sourceforge.net/lists/listinfo/ispman-docs > > > |
|
From: Atif G. <agh...@de...> - 2004-02-01 01:39:16
|
Hi Tony, Thanks for your help in documentation. It would be nice if you can place the files on the ISPMan website on sourceforge so they are available from the same place. Contact me off list so I can give you information about uploading to the website. The documentation looks great and is easily understandable. I would propose to have the CLI documentation as a separate doc. I want to write a guide on how to manage ISPMan completely without using any GUI. I will start work on it soon since I need to provide it to a client and will then integrate it with other documentations. Would you prefer to keep working in Open office or would you prefer that we setup something like WiKi, so it can be managed on line. best regards. Tony Wasson wrote: > Pheew! It's been almost a month since starting on the ISPMan Handbook, so > I'm giving an update. I've posted a First Draft of the ISPMan Handbook in > PDF, HTML and OpenOffice format. It is about 30 pages long. > > http://www.azxws.com/ispman/ > > Please let me know if you have suggestions or can expand one of the chapters. > > Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've > also added a section about Migration, with some general tips. This needs > to be expanded, since I've only done 2 migrations. > > 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 > _______________________________________________ > Ispman-docs mailing list > Isp...@li... > https://lists.sourceforge.net/lists/listinfo/ispman-docs |
|
From: Wil C. <wc...@na...> - 2004-02-01 01:50:47
|
On Sat, 2004-01-31 at 17:39, Atif Ghaffar wrote: > I would propose to have the CLI documentation as a separate doc. I would propose embedding the CLI and API docs as POD and automatically generating them. Wil --=20 Wil Cooley wc...@na... Naked Ape Consulting http://nakedape.cc * * * * Linux, UNIX, Networking and Security Solutions * * * * * Naked Ape Consulting http://nakedape.cc * * Secure E-mail Server * * Naked Ape Mail Defender http://nakedape.cc/r/md * |
|
From: Joerg D. <jo...@de...> - 2004-01-28 17:27:30
|
On Wed, 2004-01-28 at 17:25, Tony Wasson wrote: > Pheew! It's been almost a month since starting on the ISPMan Handbook, so > I'm giving an update. I've posted a First Draft of the ISPMan Handbook in > PDF, HTML and OpenOffice format. It is about 30 pages long. > > http://www.azxws.com/ispman/ > > Please let me know if you have suggestions or can expand one of the chapters. Hi Tony, when roughly flying over the manual I noticed the following: -------------------------------------- 3. Go into the unpacked ispman-1.1 direcory and do a cvs update. This applies the latest bug fixes and patches. cd ispman-1.1 apt-get install cvs cvs -z3 update -dP -------------------------------------- There is a high chance to make your ispman installation unusable by doing this ;) Since you are refering explicitly to version 1.1 you should use the "rel_1_1-bugfix" branch to only catch the bugfixes and not the untested development changes. So better add an "-r rel_1_1-bugfixes" to the last line (This will adjust with new releases of course). -------------------------------------- 4. Configure and make ISPMan. ./configure make -------------------------------------- A notice for the "--prefix" option would be nice. Not everyone wants to install to /opt/ispman. -------------------------------------- 7. For an existing installation, don't initialize LDAP, just copy the latest schema files over. cp /opt/ispman-someversion/tmp/conf/schema/* /etc/ldap/schema/ /etc/init.d/slapd restart -------------------------------------- That's problably not always sufficient. Please advice on use of "scripts/ldifupdate" to upgrade/check the LDAP DIT. Best regards, Joerg |
|
From: Atif G. <agh...@de...> - 2004-02-01 02:02:11
|
Wil Cooley wrote: > I would propose embedding the CLI and API docs as POD and automatically > generating them. 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 |
|
From: Tony W. <wa...@az...> - 2004-02-05 21:34:40
|
> Wil Cooley wrote: >> I would propose embedding the CLI and API docs as POD and automatically >> generating them. > > 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 Greetings! Splitting out the CLI information to a different document makes sense. Many users are only interested in getting it running and then using the web interface(s). However, some of us want a deeper understanding of the CLI. We could include the POD documentation along with the above "Task Oriented" information. Tony |
|
From: Tony W. <wa...@az...> - 2004-02-10 02:45:57
|
> 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 |
|
From: Atif G. <agh...@de...> - 2004-02-01 02:11:06
|
Joerg Delker wrote: Hi Joerg, your @delker.de address is getting rejected. you are subscribed with a different address? > Since you are refering explicitly to version 1.1 you should use the > "rel_1_1-bugfix" branch to only catch the bugfixes and not the untested > development changes. > So better add an "-r rel_1_1-bugfixes" to the last line (This will > adjust with new releases of course). This is not necessary since the tar ball is built from the bug fixes branch. All CVS directories have the Branch/Tag informations best regards PS: Would you like to take responsibility for managing ispman-developers mailing list? best regards |
|
From: Joerg D. <jo...@de...> - 2004-02-01 13:48:37
|
On Sun, 2004-02-01 at 03:11, Atif Ghaffar wrote: > Joerg Delker wrote: >=20 > Hi Joerg, your @delker.de address is getting rejected. you are=20 > subscribed with a different address? Hi Atif,=20 I thought you changed that last time, I'd the same problems (at least you told me so ;-) At least it's working for most of the other ispman lists, so I guess it's currently just ispman-docs that rejects that address. > > Since you are refering explicitly to version 1.1 you should use the > > "rel_1_1-bugfix" branch to only catch the bugfixes and not the untest= ed > > development changes. > > So better add an "-r rel_1_1-bugfixes" to the last line (This will > > adjust with new releases of course). >=20 > This is not necessary since the tar ball is built from the bug fixes=20 > branch. All CVS directories have the Branch/Tag informations Jep, you're right! Tony: The section is perfectly ok, don't change anything ;) > best regards >=20 > PS: Would you like to take responsibility for managing ispman-developer= s=20 > mailing list? Well, I'm honored Atif, but my time for ispman is limited to my spare time right now (and my wife isn't too happy with that ;) I would prefer to give this job to someone else here. If you like you may "add" me to the admin list, though, so I can help out if needed. Cheers, J=F6rg |
Thanks for helping keep SourceForge clean.
X