ISPConfig 3.0.3.2 is available for download. This release is a bugfix release for ISPConfig 3.0.3. For a detailed list of changes, please see the changelog section below. ===================================================== *** New! The ISPConfig 3 manual is now available! *** Version 1.1 for ISPConfig >= 3.0.3.1 (Date: 12/12/2010) Author: Falko Timme <[email protected]> 305 pages The manual can be downloaded from these two links: http://www.ispconfig.org/ispconfig-3/ispconfig-3-manual/ http://www.howtoforge.com/download-the-ispconfig-3-manual ===================================================== Download ----------------------------------------------------- The software can be downloaded here: http://downloads.sourceforge.net/ispconfig/ISPConfig-3.0.3.2.tar.gz?use_mirror= Changelog ------------------------------------ http://bugtracker.ispconfig.org/index.php?do=index&tasks=&project=3&due=50&status[]= Known Issues: -------------------------------------- Please take a look at the bugtracker: http://bugtracker.ispconfig.org BUG Reporting -------------------------------------- Please report bugs to the ISPConfig bugtracking system: http://bugtracker.ispconfig.org Supported Linux Distributions ----------------------------- - Debian Etch (4.0) - Squeeze (6.0) - Ubuntu 7.10 - 10.10 - OpenSuSE 11 - 11.3 - CentOS 5.2 - 5.5 - Fedora 9 - 14 Installation -------------------- The installation instructions for ISPConfig can be found here: http://www.ispconfig.org/ispconfig-3/documentation/ or in the text files (named INSTALL_*.txt) which are inside the docs folder of the .tar.gz file. Update -------------------- To update existing ISPConfig 3 installations, run this command on the shell: ispconfig_update.sh Select "stable" as update resource. The script will check if an updated version of ISPConfig 3 is available and then download the tar.gz and start the setup script. Detailed instructions for making a backup before you update can be found here: http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-update-ispconfig-3/ If the ISPConfig version on your server does not have this script yet, follow the manual update instructions below. Manual update instructions -------------------------- Code: cd /tmp wget [url]http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz[/url] tar xvfz ISPConfig-3-stable.tar.gz cd ispconfig3_install/install php -q update.php
Weird, tried updating my setup using ispconfig_update.sh and also manually and version is still 3.0.3.1 under Help > Version...
You are right, there was a wrong version number in one of the config files in the tar.gz. I've just uploaded a new tar.gz with correct the version number. You can either ignore the wrong version number or change it manually in /usr/local/ispconfig/interface/lib/config.inc.php and /usr/local/ispconfig/server/lib/config.inc.php. The version number has no influence on how the system works.
ISPConfig changes the configuration of services only when you select "y" for the question "Reconfigure services" during update. If you select no, then no config files will be changed. In case that you decide that ispconfig shall not update your config files, it might be that new features introduced in ispconfig will not work on your server until you manually change the config files or that bug fixes that need a config file change will not work until you manually apply the fix. So its totally up to you if you want to go the easy route and let ispconfig reconfigure the system or you want to do the reconfiguration manually.
Would it make sense to implement a feature like apt(itude) in debian has, when updating a package where a config file has changed, to display changes between the current version and the new one? This would make things easier to either manually add changes from ispconfig or to readd the own changes.
We can do this someone is willing to write these info texts for every new ispconfig version before it gets released based on the changelogs of the svn repository.
I've done some modifications to files: /usr/local/ispconfig/server/mods-available/monitor_core_module.inc.php /usr/local/ispconfig/server/plugins-available/apache2_plugin.inc.php Now after upgrading to 3.0.3.2 files are back to original. This is perfectly understandable but my question is, is there a way I can add piece of code so it wont be overwritten on upgrades?
Yes. Instead of modifying the modules and plugins that come with ispconfig, create your own custom plugins and attache them to the same events. So they get executed after the ispconfig plugin gets executed. If you think your changes might be useful for others as well, then you can propose them for inclusion into the main ispconfig code e.g. by posting them in the developer forum.
as a solution to cpanel automatic updates I use chattr I believe it will work with ispconfig updates as well try it and keep us informed Code: # chattr -V +i /path/to/file # chattr -V -i /path/to/file
I think Ben means simply make a diff on changed system configuration files as Debian apt(itude) do It would be really useful
Only a question Will it *overwrite* them, or will change/add/delete lines? I ask, because I have selected to "reconfigure services", my main.cf is modified by me, and my added lines were not changed/deleted. Is this normal? edge, what was the behaviour in your case? Overwrite or change?
Yes. As ispconfig modidfys only the parameters with postconf that it needs to administer to work correctly.
