I am trying to bend my mind around getting silverstripe to work in a Software as a service configuration where essentially there is one set of silverstripe files, but many databases and different themes, i.e.
client1.domain.com
client2.domain.com
client3.domain.com
all share the same SS3 core files (inc mysite) but each has a different theme, asset folder and database.
The purpose is so that when we upgrade the software (i.e. our modules within mysite, etc) then we only have to do it to one location and not to 100 different locations. We can the run a batch /dev/build command to update every site.
Do you think this is possible?
Thanks for any input!