You can package them as plugins. Then store each in its own repository in SVN. Then, you can use the plugin within a project by defining an svn:externals property to the repository where the plugin is stored. That way it makes it very easy to make bug-fixes etc to the plugin and update all customers using that plugin.
On Tue, Dec 1, 2009 at 4:37 AM, Paul Witschger <[email protected]>wrote: > I want to build some extras (plugins, add ons, whatever), that I can > offer to clients. These add ons will be things like photo galleries, > news article listings, blogs, etc. > > I want to put these add ons in a location where any and all projects > have access to them. I don't want to have to copy the folder structure > to their project. But, I also don't want to modify the symfony core > folder structure. Is there a way to do this? Also, would I program these > as plugins, modules, or something else? > > Sorry for these questions, but I am new to symfony (and Doctrine) and > still trying to figure everything out. > > > Thanks > > -- > > 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]<symfony-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en. > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc -- 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.
