[Chocolatey | Espreso] Habbo.com Clone CMS & Housekeeping

[The General]

I think 'sex' might be a bit inappropriate. Maybe just change it to Four Oh Four

[redk0ke]

As stated above, Espreso is not using the old HoloCMS Housekeeping UI anymore. Courtesy of my wallet, Espreso will come prepackaged with a paid heavily edited bootstrap template called Material Admin Extended (the Dark Theme you saw on some screenshots) that I'm basically integrating inside the housekeeping. Due to licensing issue, only necessary assets files will be delivered with Espreso and not the entire template archive.

Espreso Changelog 21/02/2017
* Removed all the old files from HoloCMS HK for good
* Navigation inside the application is now logged (each page request made from a user)
* All logs now have a type
* Proper handling for 404 errors
* Started system Users Management
- Added system user creation
* Added ViewServiceProvider to register controllers needed globally inside views
* Started system Roles Management
* Started Permissions system
- Implemented PermissionsFacade which allows static object instantiation for PermissionsController inside views
* Started global search feature (game users, rooms, chatlogs, furnitures etc..)

Planned for next time
* CRUD for system Roles and Users
* List and edition of permissions
* Setup artisan command to help users create the first SuperAdmin user
* First release of the global search feature
* Actually useful Dashboard
* Espreso settings

Screenshots

This looks fucking good, did give it a thought to use this admin template long time ago, but decided to use Beagle insted, so well that was probably a good idea.

Sent from my SM-G928F using Tapatalk

[Emetophobic]

I think 'sex' might be a bit inappropriate. Maybe just change it to Four Oh Four

That was the 404 page straight out of the template, I didn't change a thing, might change the text as well yes

[rockster34]

Erm.. Nope. Chocolatey doesn't uses Laravel's Public Folder for those things. Since people are too lazy to configure VirtualHosts.


Also, by default Chocolatey disables Debug Mode. Correct.

Hum.. We don't use env() settings for Chocolatey. For me Env Settings are for the Global Environment, not Chocolatey specific things xD.

-----
#UPDATES (Chocolatey)

#CODED
* Article Pagination

#FIXED
* Some small things

- - - Updated - - -

#UPDATES (Espreso)

Looks really good and clean man. Keep the work going :)

[ovflowd]

#Updates (Chocolatey)

#FIXED
* Really annoying bug of FindRetros (It's partially fixed...)
* ip_current not being updated
* Some small fixes
* Fixed Post-Install Script (composer install + composer update)

#UPDATED
* Latest Composer Dependencies

#CODED
* Now Staff's have STAFF Trait (This is used by HabboWEB)
* Coded a little Housekeeping Redirect Page (Available on Drop Down)
* Started Coding Espreso + Chocolatey Integration (only coded error page when integration didn't work)
* Coded some other stuff that I don't remember

#RELEASE
* Alpha Release of Chocolatey, Version 2.170

#IMAGES

[The General]

Would it be possible to make some kind of notice that an older version is running and then a button to just automatically upgrade (Put hotel in maintenance, create backup of files, download update package, run update sql, run tests, disable maintenance)? That way you can bring updates more often etc.

[ovflowd]

Would it be possible to make some kind of notice that an older version is running and then a button to just automatically upgrade (Put hotel in maintenance, create backup of files, download update package, run update sql, run tests, disable maintenance)? That way you can bring updates more often etc.

Yeah would be nice, but hard xD.

[redk0ke]

Yeah would be nice, but hard xD.

What's developing without a bit of harsh fun

Sent from my SM-G928F using Tapatalk

[Emetophobic]

Would it be possible to make some kind of notice that an older version is running and then a button to just automatically upgrade (Put hotel in maintenance, create backup of files, download update package, run update sql, run tests, disable maintenance)? That way you can bring updates more often etc.

That would be possible with the full framework, so I guess I can add that to the TODO list of Espreso.

One way to do it would be to grab the latest release from the "official" github repo and compare the versions (there's an API endpoint there that grabs everything). For file handling, there's a whole Filesystem library in Laravel, the commands to enable/disable the maintenance and run new database migrations would require a non-shared environment tho. (a dedicated server that you have root access to)

[The General]

Yeah would be nice, but hard xD.

Can just do a get request every once in a while to a remote server to check against the current version. If a new version is available you return something to indicate that. Then you upgrade to the next build.

And if that build is also older then you upgrade to the next build after upgrading etc. That way you can always keep the order and don't have to worry about merging version into one update package.

You can build a CMS in a month. Pretty sure you should be able to do this too.

[pel]

Can just do a get request every once in a while to a remote server to check against the current version. If a new version is available you return something to indicate that. Then you upgrade to the next build.

And if that build is also older then you upgrade to the next build after upgrading etc. That way you can always keep the order and don't have to worry about merging version into one update package.

You can build a CMS in a month. Pretty sure you should be able to do this too.

Or you make a site in the Admin Panel called "Updates", there is a button "check for updates", if there any it shows a diff of the old and new files. If the client agrees with the update, it will be installed like you described above. +1

[Joopie]

Or you make a site in the Admin Panel called "Updates", there is a button "check for updates", if there any it shows a diff of the old and new files. If the client agrees with the update, it will be installed like you described above. +1

Not sure why you want to let them see the diff of files.

Why not use the awesomeness of composer? Release your CMS in parts which can be updated with composer update.

[pel]

Not sure why you want to let them see the diff of files.

Why not use the awesomeness of composer? Release your CMS in parts which can be updated with composer update.

Idk, was just an idea I got, could be interesting for developers. So maybe make it an optional option?

[ovflowd]

I liked the @The General, @Joopie's and @Emetophobic points. The @iExit point was +-.

But i prefer doing the update be able from the Housekeeping.

We're developing an Internal "Administractive" communication API between Chocolatey + Espreso. (The Chocolatey Administractive API would be able to be consumed by anyone that have admin access, not only Espreso.. (sooo.. many applications are possible)).

Isn't good Chocolatey regularly check for Updates, since it's an php applet, not a real web service running all time. But would be possible Espreso check for updates and this makes sense.

But i doesn't think that it's good the ability of updating the Hotel by Espreso. This would make necessary Chocolatey have access to Bash (if we want to use Composer as middleware for updates).

Composer does a good job with Updating System, and we can use it. Also Laravel has the Artisan Applet that allows to create custom Console Commands.

So it's better research if we can do this by Composer or by Laravel Lumen. Regarding that Choco doesn't uses LARAVEL, but LARAVEL's Lumen Micro Framework.

A study case would be required. Since we're modeling our own APIs. Like @The General said, OK i created a CMS in a month, but i was recreating Habbo's already defined/studied APIs. This is totally different. We need analyse which would be the best way for our scenario of implementing those APIs.

Like.:
1. statistics.
2. updating.
3. control choco's template engine
4. manage choco's settings??

[ovflowd]

#UPDATES (Chocolatey)

#FIXED
* Duplicating user_settings entry when saving settings
* All values from chocolatey_users_preferences that aren't true being nulled
* Store ip_register value
* Set Angular Vendor Files to English
* Not registering because now check rank (bug created from latest release)
* Not checking if username it's inside filtered usernames. (Fixed)
* And other little bugs reported here.

#RELEASE
* Alpha Release 2.200 from Chocolatey is available now.: https://github.com/sant0ro/chocolate...ases/tag/2.200