| What is going on with Kloxo? [message #95814] |
Sun, 04 March 2012 06:02  |
 thunder11 
Messages: 395
Registered: September 2010
Location: Serbia |
Master |
|
|
Hi all,
Kloxo use to be a panel of choice for many. It seems that further implementation of features and improvement of already implemented ones became impossible.
It seems that Kloxo code hit the point where everything had to be done from scratch. A total code rewrite, or code refactoring if you wish. Devs do that all the time. Perhaps it's time for Kloxo to go that route.
It seems that raw php is dead, especially if you have such a big project as Kloxo. Long time ago someone invented Zend Framework. The code is clean and you will have more people interested in developing on something they are familiar with. Kloxo is mostly written by one guy who knew exactly what to do. It was his way, but open source is different beast and obviously old code is not suitable for maintenance anymore.
I had HUGE downtime last weekend, and from I see I'm not the only one who has one this last couple of days. This is no go, something has to be done in near future.
As a side note, redirecting domains also not working, and not that it just not working, it took down apache completely. This is disastrous. If I wasn't the one who did the redirecting all our clients websites would be inaccessible until I log in and fix things.
Also, Kloxo Dev team will have to abandon Qmail and seriously think about Postfix or Exim.
Take care.
|
|
|
|
| Re: What is going on with Kloxo? [message #95829 is a reply to message #95820] |
Sun, 04 March 2012 09:00  |
|
Hello there.
When i updated my kloxo panel few months ago, i had bunch of problems on my server, and i had to reinstall OS and install new kloxo after that. I think it was an 6.1.10 update, which looks like a horror to many webmasters, as we saw much reports of broken servers here.
I see that you still have the same problem - you publish a pack which is not tested enough, and issue high number of reports here again. Now i don't want to say what you should do, and what shouldn't, but developers need to ask if that is a good policy. I don't think that anyone want to test news versions of kloxo on public big sites, so maybe you should offer some packs to beta testers and test them fully before make it public.
I hope to see the better days for kloxo, but now i just see a software which needs more devs and beta testers in order to make stable and secure packs.
Regards.
Its better to burn out, than to fade away....
|
|
|
| Re: What is going on with Kloxo? [message #95839 is a reply to message #95820] |
Sun, 04 March 2012 13:36 |
|
mustafaramadhan wrote on Sun, 04 March 2012 07:13The problem is not testing enough before release. Many users just waiting until release and no helping enough for testing. This is the fact.
It's a serious problem. Every time an update is released we have dozens of people start posting here in a panic, because their servers are down. There's no telling how many lurkers it happens to that we never hear from.
I've complained about it a couple of times, but I get slammed for offering input so I've learned to stay quiet.
The reputation of the entire project is at stake. If largely untested updates are pushed on Kloxo users and the result is that they bring commercial servers down, Kloxo will cease to be recognized as a viable alternative to cPanel and other commercial products. That would be a terrible loss.
All we're asking is that product updates be put into beta for a week or so before being declared stable. I don't know why Kloxo developers wouldn't want that.
Entomy Networks, Linux Shared & Reseller Hosting Services
Data Centers in USA (Chicago, IL) and Europe (Zlin, CZ)
[Updated on: Sun, 04 March 2012 13:40] Report message to a moderator |
|
|
| Re: What is going on with Kloxo? [message #95840 is a reply to message #95839] |
Sun, 04 March 2012 13:49 |
|
|
mustafaramadhan, could you make it more tester friendly? For instance, offer an option to upgrade to beta releases within the control panel, and have a rollback option for when problems are encountered? This would probably draw more potential testers in. The issue is that applying test fixes is somewhat prohibitive in the amount of work it takes, and the trouble of rolling back to a working release. You cannot run a test release in a production environment, but a test release will not be thoroughly tested if it is not run in a production environment.
|
|
|
|
|
|
|
| Re: What is going on with Kloxo? [message #95851 is a reply to message #95820] |
Sun, 04 March 2012 16:41 |
|
mustafaramadhan wrote on Sun, 04 March 2012 07:13The problem is not testing enough before release. Many users just waiting until release and no helping enough for testing. This is the fact.
well to be honest with you no matter how many testers you have i think they would have run into the issues we are running into now. first thing i notice and which is alarming is when switching to lighttpd the ram usage goes down way to much. another thing is looking at the different downloads of the versions they lost about 3mb i think it was from one release to another so to me something is missing. if there is not enough testers then why release something to the normal members if you know there may be problems. smart thing would be to keep it in beta until the problems are gone or roll back when you have the whole forum complaining that the release does not work. another option is to allow us to choose what to install instead of installing the latest release because i would rather install a few releases back instead of installing the 6.1.12. before people think i am flaming the forums i would rather use kloxo than any other control panels out there and for a week now been trying to figure out what to do to keep using it. so keep up the good work in offer us a free alternative to the money grabbers out there but seriously sort the problems out on hand as far as releasing new things go.
[Updated on: Sun, 04 March 2012 16:45] Report message to a moderator |
|
|
|
|
| Re: What is going on with Kloxo? [message #95870 is a reply to message #95840] |
Mon, 05 March 2012 02:26 |
|
AviationAtom wrote on Mon, 05 March 2012 01:49mustafaramadhan, could you make it more tester friendly? For instance, offer an option to upgrade to beta releases within the control panel, and have a rollback option for when problems are encountered? This would probably draw more potential testers in. The issue is that applying test fixes is somewhat prohibitive in the amount of work it takes, and the trouble of rolling back to a working release. You cannot run a test release in a production environment, but a test release will not be thoroughly tested if it is not run in a production environment.
Since 6.1.7, Kloxo have facility to install for certain version. Say it, at this moment 6.1.12 was released but we want install 6.1.6.
Sadly, reinstall process will be destroy kloxo database and other kloxo setting (just kloxo database and not other database). Need a trick to make it's work.
I hope, I will fixed reinstall process after nginx-proxy project on my fork.
|
|
|
| Re: What is going on with Kloxo? [message #95871 is a reply to message #95847] |
Mon, 05 March 2012 02:38 |
|
thunder11 wrote on Mon, 05 March 2012 03:52Truth is that Kloxo team has insight on how things works and what's the best way to do things. Problem occours when they try to implement new feature or when you try to improve an existing one. For example, Domain redirect use to work in the first release, but at some point (it seems we have no idea when) it stopped working. Sneaky problems like this are very dangerous becuse they just appear for no reason and those problems can eventually led to serious downtime for production servers.
Kloxo developers know:
1. Advanced system administration
2. How to avoid mistakes
3. Know how the code had to be written in order to be secure
At present time, you spent much of your time finding out whats wrong rather how to improve things that work. Abandon this code until it's too late, choose you framework and you will have full featured, easy maintained and modern code in just 6 months. All you really need is 2 developers and 2 system administrators.
Original code of kloxo hard to learn and not flexible. It's the reason why I was introduce template-based webserver config together with nginx and proxy as new features on my fork ( http://forum.lxcenter.org/index.php?t=msg&th=1810 ).
If we found something wrong inside config or want add/modify something (say it, change port 80 to port 81), just modified template and then rename to custom.details.conf.tpl or custom.domains.conf.tpl. Kloxo will be know that using this files instead defaults.conf.tpl and domains.conf.tpl.
Template is 'inline php' format and that mean the same powerful like 'pure' php but more simple to read/learn.
[Updated on: Mon, 05 March 2012 02:40] Report message to a moderator |
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
