ispCP Documentation dev

Managing ispCP Daemon with CLI

Thu, 12 Aug 2010 13:05:30 +0200

The domain.php script Having the ability to create domains or services from the command line is a must for a control panel. After some effort I have created a tool to help with that. Basically the idea behind it is so you can use it altogether with rsync to migrate from other control panels (such as plesk) in a fully automated way. The objective is to code the minimum possible and use all the ispcp methods, so most of the stuff done in the scripts is to insert the new registers on the database,…

Daemon Protocol

Fri, 26 Feb 2010 15:45:53 +0200

'>>' : Message sent by client '<<' : message sent by server >> HELO\t$versione\t$token\r\n << 250\t$welcomeMessage OR 401\t$notAuthorizedMessage\r\n >> LIST SERVICE\r\n << $codeName\n$codename\n.....\r\n >> USE $codeName\r\n << 250\t$serviceChangedMessage\r\n (SQL Like) >> LIST COMMANDS\r\n (or >> LIST COMMANDS\t$codeName\r\n) << $cmdName[\t$parameters]\n$cmdName[\t$pa...\r\n >> EXEC\t$cmdName[\t$parameters]\r\n (or >> EXEC:$codeName\t$cmdName....) << 250\t$result\r\n OR 401\t$notAuthorized\r…

Files

Sun, 20 Dec 2009 16:06:42 +0200

Files The ispCP Filestructure is: / # Makefiles for all Operating Systems configs/ # Configuration Files contrib/ # 3rd Party Tools database/ # Database files for install docs/ # List of Packages and INSTALL (for all OS) engine/ # ispCP Perl Engine gui/ # Webinterface (GUI)

ispCP Functions, Classes and Libs

Thu, 01 Jul 2010 09:21:24 +0200

* ispCP_Exception_Handler and ispCP_Exception_Writer objects * ispCP_Registry object

ispCP Frontend Plugin API

Mon, 07 Jun 2010 08:01:04 +0200

Since version 1.0.6, ispCP provide a plugin API which allows for creating actions and hookings function, and methods. The functions or methods will then be run when the action is called. To be continued...

Create a Patch for ispCP

Fri, 19 Mar 2010 23:52:05 +0200

If you have made your own improvements to the ispCP code base, or if you just fixed some bugs and you want to contribute them to the community. A patch would be the right way to do so. If just one file is affected by your changes, create the patch like this: diff -uN original.php new.php > filename.patch If more then one file is affected, try this command and compare the whole trunk directory. diff -urN original_directory new_directory > filename.patch …

PERL Coding Style

Mon, 16 Nov 2009 18:06:32 +0200

The following text is a recommendation for coding. See this text as guideline. Indenting and Line Length Use an indent of 1 tab. Tab width: 4. It is recommended to keep lines length at 80 characters long for better code readability. Header Comment Blocks (VHCS Based File) #!/usr/bin/perl # ispCP ω (OMEGA) a Virtual Hosting Control Panel # Copyright (C) 2001-2006 by moleSoftware GmbH - http://www.molesoftware.com # Copyright (C) 2006-2009 by isp Control Panel - http://ispcp.net # # Version:…

PHP Coding Style

Mon, 28 Jun 2010 19:34:47 +0200

The following text is the IspCP team rules for coding. See this text as guideline. Indenting and Line Length Use an indent of 1 tab. Tab width: 4. It is recommended to keep lines length at 80 characters long for better code readability. Strings Strings are always surrounded in simple or double quotes. SQL statements are always written with back ticks:

Processes

Sun, 20 Dec 2009 17:37:26 +0200

* ispCP Release Process (v1.2) * Hotfixes & Vulnerabilities * Merge SVN * New Team Member * Bug Tracking * Election

Development

Fri, 19 Nov 2010 12:26:00 +0200

Development * PHP Coding Style * PERL Coding Style * Translate ispCP * Create a Patch for ispCP * Filestructure * Managing ispCP Daemon with CLI * Processes * Install / Update Errors in Omega 1.0.3 discovered

Translate ispCP

Thu, 15 Jan 2009 13:25:45 +0200

If you've translated Unix/Linux applications before, you might already know the GNU gettext tool library. If you do so, you can immediately start translating by using the .po files in the languages-files directory. If you are new to the GNU gettext tool library and concepts, read on.

SVN Guide Lines (Working Draft)

Sat, 27 Mar 2010 19:22:22 +0200

feature: A feature is a new introduced distinguishing characteristic of a software item. It will be called feature as long as it is not part of the code base. trunk: trunk is the main development branch for the project(s). It underlies several rules, stated in .