thank you for your reply.
it's a pity that the architecture that xampp proposes does not allow for multiple environments on the same host.
a normal practice of that i apply to oracle environment which is an area where i have 20 years experience is to install oracle rdbms software, application sofware, database datafiles, etc, all under one directory, for example:
-> db (database software)
-> data (database datafiles)
-> ora (application server software)
-> appl (application files, such as jsp, sql, rdf [reports], fmx [forms], etc)
in that way it is possible to have virtually an unlimited number of environments within one host, for example:
one of the reasons why this particular architecture is very beneficial is where you need to apply a particular patch or upgrade a particular piece of software for one environment but you don't know whether that change is going to have any negative side-effects on any of the other environments running on the same host...
another reason is that by keeping each environment independent, cloning procedures of an environment could be implemented, where each clone is still a completely independent entity... for instance you might want to clone your production environment into a new development environment where you want to test a new version of php, while your functional analysts are still functionally configuring on your testing environment for a certain release of your product and your users community is doing user acceptance testing on yet another user acceptance testing environment... and all of these environments can coexist (with the possible exception of the production environment if your budget can help it) on the same host...
obviously if the xampp is installed by default on /opt/lampp and there is no way of reconfiguring this, then this option is not viable... but i was curious to see if anybody had already considered this option...
i wonder how you solve the problem of creating moltiple environments on the same host, for example a development environment which uses a certain release of xampp in order to support possible changes to be made to the current production environment, and a development environment which uses the next release of xampp where you are working on the next upgrade of your production environment? any view on your practice would be most welcome...