search

silexphp / Silex-Skeleton

A skeleton to get started with Silex
MIT License
780 stars 197 forks source link

E_NOT_MICROFRAMEWORK? #33

Closed Ocramius closed 9 years ago

Ocramius commented 9 years ago

Not to be too pushy, but doesn't this kind of approach pretty much defeat the point of using Silex at all?

Just a question to understand why the need for this skeleton: result of the discussion should probably land in README.md

oscherler commented 9 years ago

I can see it as a source of inspiration. If my project grows, I have an example of how to organise it.

dominikzogg commented 9 years ago

@Ocramius Cause silex scales well, there is no technical reason to not structure it

javiereguiluz commented 9 years ago

I personally use Silex a lot and I always start my projects with this great skeleton. In fact, I'd love to have it as the default structure for new Silex projects. In my opinion this structure is the best way to organize common Silex apps.

Ocramius commented 9 years ago

Closing: satisfied by the responses.

While I see where this is going and why, I'll keep my own Silex apps as single-page apps that actually move to a controller-based dispatching mechanism when they grow (having controllers being actual services), so this skeleton is a half-way solution to that.