Decouple from Laravel

[tobyzerner]

_1 Upvote_ From tobyzerner.com/mithril:

Instead of using the whole framework, we will explicitly pull in components and tie everything together with a custom bootstrapping process. This will allow us to optimize performance and provide better integration with existing applications.

I thought I'd create an issue so we can (a) work out exactly what needs to be done and (b) keep track of it.

fluxbb/fluxbb#2.0 and fluxbb/core are obviously good inspiration :)

• [x] Implement a custom router
• [x] Explicitly pull in only the Illuminate components that we need
• [x] Pull in a PSR-7 implementation (probably the one by @phly, which has now moved to Zend)
• [x] Pull in a PSR-7 middleware stack (zend-stratigility) to the skeleton repository. This will replace Laravel's HTTP kernel.
• [x] Convert the different parts (frontend, admin and API) of the app to separate middlewares that can be mounted independently. This should also speed up routing because only the routes for the proper middleware need to be parsed. (Special attention to route generation, because we do need all routes there.)
• [x] Hook this up with a container instance (an application class?) and load our service providers
• [x] Implement a config system: config.php for database details, everything else in a ConfigRepository (database)
• [ ] Provide integration with Laravel (possibly via a separate package), basically bridging the Symfony HTTP kernel to PSR-7.
• [x] Review and update the Composer requirements (Laravel 5.1, PHP 5.5, ...)

@franzliedke I'm dying for your input here :D I'm happy to do anything you want to delegate, I really want to get this moving :)

[Allineer]

guys, look at this

[franzliedke]

We'll likely go with nikic's FastRouter.

[BenOvermyer]

If you're decoupling from Laravel, why not decouple from PHP?

[qrokodial]

@BenOvermyer

If you're decoupling from Laravel, why not decouple from PHP?

because Flarum needs to be able to be easily ran almost anywhere, and PHP is universally supported throughout all web hosts.

[BenOvermyer]

That's fair reasoning. MySQL datastore, then?

[franzliedke]

MySQL is supported, as are several others (the ones that Laravel's database component supports).

[BenOvermyer]

What templating engine are you using? I don't see Twig; are you using Blade at the moment?

[franzliedke]

Yep.

[BenOvermyer]

Decoupling from Laravel would be best served by using an independent templating engine. I recommend Twig, having used it to great success myself.

[franzliedke]

It's okay to use some of the Laravel components, we're just trying not to tie ourselves to its default structure too much.

[BenOvermyer]

Again, fair. My recommendation stands, though. ;)

[franzliedke]

Let's discuss the whole Twig thing on the development forums. These kind of things are not yet set in stone, so you might convince us by listing its special powers. ;)

[BenOvermyer]

Will do!

[franzliedke]

The actual decoupling from Laravel's foundation is almost finished, next up: pulling in only the components that are needed and setting them up by hand.

[franzliedke]

For anybody watching this: I just merged the psr-7 branch into master. This will be awesome! =)

[rodrigoargumedo]

+1 :smile:

[BenOvermyer]

Fantastic. =D

[tobyzerner]

This is basically done - Laravel integration is another issue :)