On 06.01.2011, at 14:34, Jordi Boggiano wrote: > On 06.01.2011 14:31, Lukas Kahwe Smith wrote: >> >> On 06.01.2011, at 14:28, Jordi Boggiano wrote: >> >>> On 06.01.2011 12:48, Lukas Kahwe Smith wrote: >>>>> This can be easily achieved when making a copy of the assets but I don't >>>>> see how it could work when using the --symlink option. >>>> >>>> >>>> Maybe instead of symlink we should use mod_rewrite handling magic? >>> >>> mod_rewrite isn't possible, you could dynamically define Aliases to >>> paths, but that's essentially the same as symlink, and defining aliases >>> to files would fix it but it is just crazy you'd have potentially >>> hundreds of aliases in your .htaccess. >> >> >> How so? >> mod_rewrite would first check if the file exists in the Application dir and >> if not fallback to the Bundle dir. > > AFAIK mod_rewrite only rewrites the URL, if the file is not in a > publicly accessible dir, it won't work, and you don't want to have your > entire src/ accessible from the web.
ok for production you want to copy. so this is really only a dev issue. so you would symlink both dirs. all links would have to point to the application version and fallback to the bundle version or something like that. i am pretty sure it can be done .. but will require some fiddeling and it will potentially feel a bit iffy. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
