1
0
Fork 0
old gnuviechadmin version that is not developed anymore
Find a file
Jan Dittberner bca6369b41 SessionManager and client-server communication implemented
git-svn-id: file:///home/www/usr01/svn/gnuviechadmin/gnuviech.info/gnuviechadmin/trunk@185 a67ec6bc-e5d5-0310-a910-815c51eb3124
2006-04-17 19:20:14 +00:00
backend SessionManager and client-server communication implemented 2006-04-17 19:20:14 +00:00
backend.old added code from older repository 2005-09-14 21:45:52 +00:00
common ZSI-services 2006-03-15 23:19:00 +00:00
frontend/common SessionManager and client-server communication implemented 2006-04-17 19:20:14 +00:00
gnome-frontend/src ZSI-services 2006-03-15 23:19:00 +00:00
php - SOAP interface for PHP 2006-02-21 19:51:23 +00:00
AUTHOR first thoughts 2003-11-23 09:43:31 +00:00
config.php add sample configuration file 2004-05-10 19:22:38 +00:00
database.sql added unique indexed column sysuid to sysuser table 2003-11-23 19:42:21 +00:00
LICENSE first thoughts 2003-11-23 09:43:31 +00:00
Makefile clean target 2003-12-20 13:20:29 +00:00
README first thoughts 2003-11-23 09:43:31 +00:00
TODO Added statistics to TODO 2003-12-21 00:17:12 +00:00

gnuviechadmin aims to be a server administration tool originally
developed for managing gnuviech.info.

gnuviechadmin is targeted for Debian GNU/Linux 3.0r2 (woody) but may
be ported to later Debian GNU/Linux releases in the future.

application design thoughts
===========================

I think a 2-layered architecture will be best.

One layer (which needs to be run as root) does all the background work
(like creating users, zone files ...). This layer will be implemented
in python and will invoke several Debian system utilities.

The second layer will in the first place be a PHP based Web frontend
where the administrator can manage the servers most common
tasks. Later there will be support for client and reseller frontends
for tasks that the administrator allows them.

The second layer may also be a GUI application if the need arrises.

Both layers will be coupled through a sql database. I will use
PostgreSQL, but as the need arrises I'll also try to support other
databases.


  +----------+                        +---------+
  | frontend |                        | backend |
  +-----+----+                        +---+-----+
	|          +----------+           |
	+--------->| database |<----------+
                   +----------+