Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 May 2003 21:17:25 +0400 (MSD)
From:      "."@babolo.ru
To:        Maksym Shevchenko <r0land@r0land.kiev.ua>
Cc:        omestre@freeshell.org
Subject:   Re: production...
Message-ID:  <200305201717.h4KHHPIK095379@aaz.links.ru>
In-Reply-To: <034601c31ee9$0d4cdc20$8300a8c0@pepelac>

next in thread | previous in thread | raw e-mail | index | archive | help
> Hello, Artem!
> 
> It is possible that he means other thing useful. As example, in hosting
> solutions with a numbers of hosting on each server, keeping configuration of
> each service (as usual - dns, mail, http (dynamic & static content), ftp,
> telnet/ssh, some kind of sql) in decentralized files are not too simply. I
> never seen systems (but had try to build) that will keep configuration for
> such hosting centralized database (possible with simply export to usual
> configuration files).
> For instance in such tree:
> ----------------------[begin of instance]---------------------------
> 1) Agreement information
>     a. Contact information
>     b. Agreement number
>     c. Expire date
>     d. ...
> 2) DNS
>     a. Allowed
>     b. Primary "superns1.superhosting.com"
>     c. Secondary "superns2.superhosting.com"
>     d. Name zone 1 (SOA entry)
>         i.  Entry
>         ii. ...
>     e. Name zone 2
>         i. Entry (MX)
>         ii. Entry (IN A)
>         iii. ...
> 3) Mail
>     a. SMTP
>         i. Disallowed
>         ii. ...
>     b. POP3
>         i. Allowed
>         ii. ...
> 4) Web Hosting
>     a.  Allowed server "apache043.superhosting.com"
>         i. Root dir "$HOME_APACHE043/user/htdocs"
>         ii.  CGI dir "$HOME_APACHE043/user/cgi-bin"
>         iii. ...
> 5) Ftp
>     a. Allowed server "apache043.superhosting.com"
>     b. ...
> 6) Telnet/SSH
>     a. Disallowed
> 7) SQL
>     a. PostgreSQL
>         i.  Disallowed
>     b. MySQL
>         i. Allowed server apache043.superhosting.com"
>             1. Data dir "/home/user/sql/data"
>             2. Used local socket "/home/user/sql/sock.tmp"
>             3. Network socket "disallowed"
>             4. Bin dir
>             5. ...
> ----------------------[end of instance]----------------------
> 
> What about such centralized configuration systems?
Part of this work is http://free.babolo.ru/ports/jailup/
(BSD license)
and some is ISPMS/ISPDB (restricted),
very old version for evaluation is
http://free.babolo.ru/ports/ispms/

Yes, not all needs done yet.

-- 
@BABOLO      http://links.ru/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305201717.h4KHHPIK095379>