The work on the 3.1.14 version has been finished and is available as a release candidate version for testing now. This version fixes many bugs and provides also some nice new features like the new datalog viewer (in the monitor module) which allows the admin to see what has been changed by a user in ISPConfig in detail. The datalog viewer provides an undo function as well. When a customer calls you next time ... "my website stopped working and I have not changed anything" ... then you know now where to look first. Changelog: https://git.ispconfig.org/ispconfig/ispconfig3/milestones/65 You can download the release candidate version here: https://www.ispconfig.org/downloads/ISPConfig-3.1.14rc1.tar.gz If you want to test it, use these steps to update an existing system to 3.1.14rc1: Code: cd /tmp wget https://www.ispconfig.org/downloads/ISPConfig-3.1.14rc1.tar.gz tar xfz ISPConfig-3.1.14rc1.tar.gz cd ispconfig3_install/install/ php update.php Have a nice weekend!
damn, that's every customer call isn't it? seriously though, the undo function would be a really useful feature. does that allow undoing a number of individual datalog changes, or does it undo everything after that point? I would install it on my servers to see, but i'm really paranoid about putting any beta/rc software on a live server, and I don't have time at the moment to do any testing.
The undo function reverses exactly the change of that datalog entry. So when you switched e.g. from php-fpm to php-fcgi and later enabled Perl in the website and you press undo in the php change datalog entry, then only the php mode will get switched back and not the perl activation.
Nice work, awesome feature Btw, is that compatible with Debian 10 (Buster)'s AppArmour feature, in your perfect server setup of ubuntu, you have always disabled AppArmour package, but no in perfect server setup of Debian 10. Is it supported now. Thanks Till
I guess that Apparmor's default settings are not that strict in Debian 10, at least I have not encountered issues with having it acticvated yet, that's why it's on. On ISPConfig side there are no changes implemented.
Thanks for your work. I'll try to download the latest version and test it. P. S. I'm new around here. it's good to see the project is actively worked on. After the largest shoot-yourself-in-the-foot movement in history by cPanel (change of licensing model), I'm guessing you'll receive a lot of new users, many of them companies.
I've heard of that too as several companies contacted me to get help switching their infrastructure from CPanel to ISPConfig. We are currently working to get CPanel support built into the ISPConfig Migration tool. I'll expect it to be finished in August.
Welcome to the community, I left cPanel and Plesk years ago, not because of pricing but the level of custimization, control on each package, managing other server related stuffs, they are limited and give us limitation on many things. ISPconfig gives us full control over everything. One more thing, everyone please contribute to this project by one or others means.
Yes, this is the biggest (and I mean it seriously) candidate for the shoot-yourself-in-the-foot Academy Award. Even if they roll back this decision, the hosting environment trust has been severely damaged (counting the fact that cPanel was acquired by Oakley Capital, it doesn't belong to the previous long-term owner). While I'm not happy with the path cPanel chose, I'm happy to see projects like this being considered as a replacement. The "power" is back in the hands of community.
