Hi. Right as you said - I'm ignoring web/*Plugin and doing symfony plugin:publish-assets after every update.
I also think this snippet should look like > rm web/*Plugin > symfony plugin:publish-assets > since you may delete some plugins during development. 2009/3/17 Yevgeniy A. Viktorov <[email protected]> > > > Summary of solution discussed in this thread: > 1. use some task(sf12: symfony plugin:publish-assets) to symlink/copy > assets of your plugins to web dir. > 2. add svn:ignore property to your "web/" folder (*Plugin) > > Thanks. > > Tom Haskins-Vaughan wrote: > > Hi I've just come across this scenario, but I don't fully understand the > > solution. > > > > Would it be possible to do an svn:externals link to the plugin's assets > > in the repository? > > > > Tom > > > > Bernhard Schussek wrote: > > > >> Hi Thomas, > >> > >> On Thu, Feb 26, 2009 at 10:19 AM, Thomas Rabaix < > [email protected]> wrote: > >> > >>> You can define a svn:ignore property to the web folder and just call > the > >>> task on your server to publish plugin's assets > >>> > >> Simple yet effective. I assumed that svn:ignore would not work because > >> the asset folders are already under version control, but it works > >> because the symlinks themselves are not. > >> > >> I just added *Plugin to svn:ignore and it works wery well. > >> > >> > >> Thank you! > >> > >> > > > > > > > > -- With the best regards, Andy. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
