Guys, just calm down. For those doesn't know why this Housekeeping was released, there are some points:
I personally asked to the author release it, since I closed the Official Chocolatey Development for unknown time, due to lack of time for doing it, and lack of developers that want to contribute to it.
Actually Chocolatey it's the onliest CMS available that creates a 100% exact replica from Habbo.com. New CMS's are being developed, but until that we just have Chocolatey.
The main reason of just stopping updating Chocolatey, it's simple (also the main reason was just the lack of time), but the second biggest one, was the poor tech stack. Obviously we can see that the Habbo.com CMS it's made with Angular and at least Node.js or Vue.js, we can actually seer that it's basically impossible editing the front end layer of Chocolatey since all te assets are actually compiled (even the CSS, JS and Images).
The right way was since from the beginning, using Sass or Less for stylizing, some ImagePack Library for generating the image bundles, and NodeJS or VueJS in order to create the Angular modules, and packing it. Also NodeJS would be a better fit for the backend.
I could use Lumen for it, If literally Lumen was only being used for the backend, but I did a bad use of Laravel's Lumen, using a Micro Framework made for API handling also Frontend.
Laravel's also has the Laravel Mix package for Node, that allows packaging modules, but JSPM would be a better fit.
Also for the backend I personally would choose Groovy + Grails or just Java + Spring Boot or just NodeJS.
Chocolatey was an experiment that made success and popular, but I actually knew since from the beginning that maintaining it and adding new features would be practically impossible.
The fact it's that creating a good coded CMS, and well packaged with a decent tech stack really would spend my time more than was actually spent.
I'm really happy that @
LeChris is doing a decent "replica" of Habbo.com (I can't say it's a replica/clone because he's adding custom stuff).
Yes, this HK has vulnerabilities, if you're just bothered with that, and want to use it, fix yourself.
The OP shared it because I asked, and a lot of people want continue to use Chocolatey because even not being a piece of art in terms of code, it's actually a gem in terms of what we have for Habbo Retro CMS's.
I would love if people just collaborate and help each other improving this HK.
I also probably when getting more time, would ask to @
LeChris if I can team up with him and help him in his CMS. If he really manage to do a decent job on it, rapidly will surpass chocolatey.
I'm really sorry for not having time to continuing Chocolatey, after seeing @
LeChris work I was both happy and sad. Happy because someone it's doing a great job, sad because the days of Chocolatey were in their end.
Thanks for all the support of everyone!
