is it worth migrating CChits to work with a framework like laravel, or Code Igniter?

[computamike]

I've had a look through the code, and I was wondering if it would be worth refactoring the code to operate within a MVC framework? I'd be interested in having a go at this if this is something worth while - I've been working with MVC frameworks at work, and been mainly supported Code Igniter.

I think this would make the codebase more accessible for other developers with experience of Code Igniter or Laravel.

[ymauray]

Hello Mike.

Although this is a valid and interesting idea, we are in the process of trying to split the API and the UI.

We would like to build a backend on top of Slim and Medoo. When we have that ready, we will revamp the UI to make it use the API backend. Our site would then just be another client of our API, alongside anything else that would make use of it. That way, we only have one piece of software to maintain should we find bugs in the backend.

Laravel could be a good candidate for the revamped UI, however, since the hard work will take place in the backend, it makes more sense to use a client side framework like VueJS or Angular and any of the 42 javascript framework that will pop up in the next few weeks :-) .

Now, as I said, when the API is ready, the door will be opened for multiple clients, so feel free when that time comes to write your own using Laravel !

Keep hanging around here and we'll let you know how the API backend goes !