Skilled Illusionist
- Joined
- Jan 27, 2012
- Messages
- 382
- Reaction score
- 343
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
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.
#UPDATES (Chocolatey)
#FIXED
* AngularJS locales to match Default English
* A little weird typo preventing of HabboWEB loading the Group Badges in Angular.
* Some other minimal bugs
#CODED
* Don't show banned users profiles like Habbo
* Don't show invisible room's on the room gallery
#BACKLOG
* Code NUX Rooms
* Code Facebook Integration (boring)
* Other Features.
#ASKING
* People if you see a cool feature that you want be on Chocolatey, or some feature that I didn't replicate from Habbo. Or some feature that doesn't is working exactly like as from Habbo, create an Issue on the Chocolatey's GitHub repository,
#PHPUNIT
* In the future I will code API tests for all Routes and Assignments Test's (White Box Tests). To check if in each new RELEASE I broke something. (This feature can delay a bunch of time)
#SOME FEATURE REQUESTS
* I received a feature request to code the Habbo Help Center. I will not like to code it, since Habbo's use Zendesk. I can create something LITE that uses the same design. The "Help Center" would also be a separated module. But in this case would be Laravel.
Like Espreso it's a separated module. This Help Center would also be a separated module.
If the community wants me to code this, I ask for a minimum of 10 votes for this. Also, I would appreciate a "name" for this "CMS".
Like "Banana" or "Cookie Help"... I dunno.
Thanks for supporting this project!
As I said, IIS Compatibility it's a Backlog Item.I'm getting a 500 - Internal error trying this on IIS.You must be registered to see links
* Something is wrong with PHP, not the cms. Just forget I said anything.
Is it NGINX & HHVM compatible?As I said, IIS Compatibility it's a Backlog Item.
That means.: not coded yet..
Backlog = Next Items to Do, in some way.
Is it NGINX & HHVM compatible?
.htaccess can easily be converted to NGINXs configuration, I was more wondering if your CMS depends on certain PHP7 featuresI never tested on NGINX. And I never seen anyone with Habbo using NGINX...
As far I remember NGINX has a module that allows Apache MOD_REWRITE usage.
So, I think, yes.
HHVM has included multiple PHP7 features, you just have to enable them manuallyIt might not like HipHop since it depends on PHP7's new syntax changes, so it probably won't work with HHVM. I haven't followed that project in a while though, maybe they have parity with PHP7 now?
HHVM has included multiple PHP7 features, you just have to enable them manually
Yeah I know haha. But this is a heavy framework (if Laravel and not Lumen) even for such a small CMS.You don't really need to use HHVM, this CMS is heavier on resources than actual code execution. NGINX for static files would be highly recommended if you're getting a lot of traffic but standard PHP should be totally fine.
I'm not sure what their extent of PHP7 support is, odds are it'll break something.
Yeah I know haha. But this is a heavy framework (if Laravel and not Lumen) even for such a small CMS.