Lukas Kahwe Smith wrote: > Lukas Kahwe Smith wrote: >> Lukas Kahwe Smith wrote: >> >>> The development case when I do not bother to setup a vhost. I am sure >>> there is a cleaner/better solution. Ideas? >> Something that will probably work much better would be to be able to >> change the relative url used in the AssetHelper. As a matter of fact I >> only had to change the _compute_public_path() method accordingly. Seems >> like a slightly cleaner solution. > > I just added the following to our internal wiki. I do not claim that it > will win a beauty contest .. maybe it should become a standard feature > in symfony to prevent the newbie mistake of deploying with a development > frontend controller in place?
sorry for the spam .. i did not mean that my hack should become a standard, but maybe some way to define the asset host via a callback or something. This would also be nice for people leveraging a dedicated image host (S3 etc.). regards, Lukas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
