That is - I'd like a few customers run off the same codebase (which will
segment them on the OXID) and still offer each customer 'his' own public
with css, javascripts, images, uploaded files etc
Does anyone here known if this will even work - or am I just rambling?
I do
something like that. I have a directory containing a normal ROR
setup (we will call that ROR), I use a simple virtual host
setup (this is extracted from the script that sets things up)
with each DocumentRoot parent directory being a directory with
symbolic links to the stuff in ROR created by:
I then
overwrite the db config file to contain the database info
specific to the customer. I share the files in public but
one could follow the same paradigm and make them specific to
the customer. It works well for me and I have only one code
base with distinct databases and logfiles etc. Nothing in
the code has any concept of there being multiple users of
the code. It is just shared code. This is a 2.2.2
configuration and it might change a bit for another version
but I would imagine the same concepts would work.
I just create two separate folders but have them point to the same svn
repository. Then I have a file called skin.yml (not checked in) that
contains any data that differentiates them. So the files are
duplicated, but they are always in sync because I deploy both sites in
parallel.
