Alternate directory naming for multi site installation
hello everybody,
is there any known alternative way to tell drupal the site path without using the directory naming convention?
our usecase:
i am developing in a team and we are using eclipse as IDE and subversion for revision management. we are new to drupal and currently thinking about an intelligent workflow for our development. i thougt about using a multisite drupal installation for development purposes on each developer's machine. each project could be realized as one site in the multisite environment.
every workstation has got its own name (and ip) and the current development state of a project can be accessed via http://WS_NAME/PROJECTNAME
so the url for each specific site in the drupal sites-directory is different on every developer's workstation. and renaming the folder on every workstation to the proper name causes traceability-problems while using subversion.
it would be greate to be free to name the site's subdiretory with any name and to configure the possible base-urls of the site in any config file.
this would also help to quick change the path to the site (e.g. to rename the subdomain) without having any structural changes or to have multiple paths pointing on the same site.
greetings,
dave
I don't know if I have
I don't know if I have understood everything because my english is far from good, but you spoke about a centralized
project development, right.
I have tested following modules and there are great:
http://drupal.org/project/domain
http://drupal.org/project/subdomain
there are others, like
http://drupal.org/project/subdomain_manager
http://drupal.org/project/multisite_manager
do not remember yet if they are all upgrade to Drupal 6 but I tested Domain.module and if
you can access your DNS Server and setting how is described in "documentation" you can almost
do what ever You want with it.
Hope this helped
Cheers - Wolfflow
If you look at word and nouns you do not clearly understand take a look at Common Terminology, Feel free to propose missing Terms
i'll try
hi,
thank you for your reply. maybe the domain_manager module could solve my problem, but i have to wait till its drupal6 release is not alpha any more...
when i read your post, i think i did not really make clear my point. (my english is not that good either ;) )
for example we have two developers working on the same project. the workstation of developer1 is called comp1 and the workstation of developer2 is called comp2. both are working on the project coolproject.
now it is possible to access the current development state of the project of developer1 via http://comp1/coolproject and the same project developer2's machine is reachable via http://comp2/coolproject
all data stored in the database is no problem for this situation but the problem lays in workstation-specific configuration information in files or the filesystem-structure, because we are working with subversion and thus sharing the current development-state. the settings.php is just ingnored in our subverion. so each developer can have his own file.
in the case of the multisites, the directory-names provide configuration-information themselves. i don't want to merge data between multisite installations. all i want is a possibility to have a multisite installation, where the name of the site's directory has nothing todo with it's URI.
that means, the host-name which this site listens to is stored anywhere else. in the database, in a config file, etc. then we are able to share our directory structure, even if the domain changes.
i'll test the domain managers. - maybe this helps me... thanks again for the info :)
greetings,
dave
I had one's a similar
I had one's a similar configuration to do, if of course I have fully focused your needs. I installed Drupal 6 within one database with different sub-domain names but i shared the table that are needed for control access from the main domain. I cleaned-up all duplicate tables and left that ones for each sub-domain, then repeat the install.script with a different sub-domain and so on .... Finally I had to setup a bit the .htaccess of the host to redirect and rename routing for the different sub-domains, what I get is that User with the right access-privilage could have control from one place about the whole sub-domain package.
Hope this was not useless
Cheers - Wolfflow
If you look at word and nouns you do not clearly understand take a look at Common Terminology, Feel free to propose missing Terms
I have a similar issue. When
I have a similar issue. When moving the site from development to staging to deployment the URL changes, i.e. from http://localhost/site-alias to http://staging-server/site-alias to http://www.the-production-url.com.
Having to change the /sites/sitealias directory is cumbersome and often leads to errors, since the directory name is stored in the database.
I have tried using symbolic links but for Windows deployments I would like a more elegant approach. Is there such a thing?
--
CODESIGN Studios
Life, The Universe, and Everthing - A day in the life of an audio visual junkie