Closed evandertino closed 11 years ago
Define multi site funcationality?
You can already change config values based on the domain name (see environment configuration) You can define routes for different domains, including wild cards You can work with multiple databases
Please be more explicit.
I don't know what this means. Ask in the forums?
I think what this is referring to is something that would allow multiple "sites" to function off of the same Laravel Core by allowing multiple /public directories. Say an admin panel and the site it administers. Models and some other parts could be shared.
That said, making components that are auto-loadable by composer is a much better approach to managing cross project dependencies, even ones specific to your own set of applications.
This is already possible, just copy your public directory. Possibly make paths.php more dynamic, but very easy to do.
am testing on paths.php with multiple domains, so far its good to go, multiple public folders same core, different routes
I really think you guys already have the solution to the problem (Using one codebase for multiple domains) but out there in the wild, the idea is still strange, even to me. can someone just write an article on this.
Will very much appreciate.
Multiple public folders doesn't solve the "single application - multiple presentations" problem:
Requirements:
Real world scenarios: a) Fontend & Admin of an application b) Themes!
Proposal:
Hey, sorry if I'm shooting the moon... I'm still digging into Laravel Cheers!
I have got such a concept implemented on CodeIgniter - https://github.com/ivantcholakov/starter-public-edition-4. If you like some ideas that might be applicable for Laravel, take them. My typical applications are front-end and admin-panel, but other architectures are possible too. Good luck!
Please include multisite functionality into laravel 4, it will really help with portability of the framework