How do common web frameworks (Django, Rails, Symfony, etc.) handle multiple instances of the same plugin?

Question

Does any of the popular web frameworks solve this problem?

Here's an example: suppose you use one of these web frameworks and want to install a blog plugin. With the exception of one blog, you need to run two separate instances of the blog plugin, and you want them to be separate.

Or say you want to install multiple instances of the user authentication plugin because you want to separate your users from your user accounts.

Or say you want to install multiple instances of the wiki plugin for different parts of your site, or multiple instances of the comment plugin, or something else.

It seems to me that at the basic level, each instance of the plugin should be able to configure using a different set of database tables and should be "installed" with a different URL.

My experience is mainly related to Django and Symfony, and I have not seen a clean solution to this problem in any of them. They both tend to assume that each plugin (or application, in the case of Django) will only ever be installed once.

I'm curious if the Rails people figured out a clean solution to this problem or any other framework authors (in any language).

And if you are going to develop a solution to this problem, what would it look like?

Answer 1

It will look like BlogFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactoryFactory...

Answer 2

Ruby/Rails, , . ( , , , STI.) .