Asset Passthough

[aaranmcguire]

Not sure if the title makes sense, but I was wondering can you think of any way to allow each theme to be self contained and not require publishing of the assets to the public folder?

The reason I'm wanting this is I'm wanting to create a multi-tenant website with the ability for users to have there own theme, at first it's only going to be themes I generate but in the future I hope to open that up to uploadable themes. The issue I foresee is I'm going to have theme files in two locations and it's going to become difficult to manage.

The only ways I can think of doing it are:

• Putting the themes directory in the public area (making blade files publicly accessible - sorta)
• Creating a route that reads and outputs the folders content (would reduce load time as php/hhvm would have to read and dump the file vs nginx directly).

Can you think of anything, even if it is the 2nd option.. Can it be added into this package or does it have to be done manually?

Thanks

[tankerkiller125]

If you have a dashboard you can have Artian run commands using the Artisan class. I have personally used this to publish the files. Also having the blade files in a publicly readable directory could become a security concern.