Hope no-one is going to bite off my head for kind of posting twice, but I think this could be a better forum for this topic.

I'd like to make my own control panel for a RaQ(3) in perl. I have seen alot of control panel's out there (mostly coded in php) but was wondering first of all if it is possible to;

a) code a (simple) control panel for adminstration of user accounts and setting up e-mail addresses etc. in Perl

b) how can I let a .pl/.cgi file have access to edit RaQ files as appropiate for user account set up etc.


By the way, what language is the default RaQ control panel coded in, it looks like some of the files have a .cgi ext ?

cobalt uses perl for most of the control panel... If you open those .cgi files you will probably find perl scripting in there.

Originally posted by just1post
b) how can I let a .pl/.cgi file have access to edit RaQ files as appropiate for user account set up etc.

I'm not familiar with how RaQ's are set up, but I'm guessing you'll need root access to make those changes. I would take the strategy of how web.cp is set up and have a perl script running in the background as root and feeding tasks that need root permissions to it. Alternatively, you could use C or another compiled language for your routines that require root access and chown it root, and give it setuid permissions.

Originally posted by just1post
Hope no-one is going to bite off my head for kind of posting twice, but I think this could be a better forum for this topic.

I'd like to make my own control panel for a RaQ(3) in perl. I have seen alot of control panel's out there (mostly coded in php) but was wondering first of all if it is possible to;

a) code a (simple) control panel for adminstration of user accounts and setting up e-mail addresses etc. in Perl

b) how can I let a .pl/.cgi file have access to edit RaQ files as appropiate for user account set up etc.


By the way, what language is the default RaQ control panel coded in, it looks like some of the files have a .cgi ext ?

a) No such thing as a simple control panel (especially on cobalt)
b) Your perl scripts can use cobalts files their ".pm" cobalt files (i think they call it special sauce?)

My honest advice, is unless you know alot about linux and the cobalt cp, dont try it. The cobalt CP is tightly closed into the os. Modifications to OS will piss off the cobalt cp to no avail (pardon the language)
I would especially discourage it on a machine where you already have hosting customers?
If you want your own cp, you have wasted money on a crappy cobalt just for the cp :(

Just my $.02