php - What would the Laravel 5 directory structure look like for serving multiple sites and APIs? -
say have multiple "sites" (ie. backend, public frontend, private-pay-for frontend, mobile) , perhaps offer api widget services or android app. sites need (at least initially) share same laravel instance , sharing services (ie. frontend site might call few services backend site, or backend site , api might share services, since i'm using soc things presentation logic).
looking @ userscape's project snappy, taylor otwell says renamed models
folder called snappy
, added more folders various "areas of responsibility". in laravel 4 however.
here's laravel 5 directory default directory structure:
app <-- should rename , duplicate backend, frontend, api...? commands console events exceptions handlers http controllers <-- or add subfolders in controllers backend, frontend, api...? middleware requests providers services <-- , add subfolders in services backend, frontend, api...? bootstrap config database public resources storage tests vendor
how should approach directory structure in laravel 5 such situations (keeping in mind concerns of namespacing)? didn't catch guidance on docs.
Comments
Post a Comment