From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 10:11:02 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A0BF37B401 for ; Tue, 20 May 2003 10:11:02 -0700 (PDT) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id F215B43FAF for ; Tue, 20 May 2003 10:11:00 -0700 (PDT) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.7/8.12.6) with ESMTP id h4KHHRJN095380; Tue, 20 May 2003 21:17:27 +0400 (MSD) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.7/8.12.6/Submit) id h4KHHPIK095379; Tue, 20 May 2003 21:17:25 +0400 (MSD) Message-Id: <200305201717.h4KHHPIK095379@aaz.links.ru> X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <034601c31ee9$0d4cdc20$8300a8c0@pepelac> To: Maksym Shevchenko Date: Tue, 20 May 2003 21:17:25 +0400 (MSD) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 cc: freebsd-hackers@freebsd.org cc: omestre@freeshell.org Subject: Re: production... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 17:11:02 -0000 > 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/