The initial situation looks like this:
- The corporate software is PHP-based.
- It is delivered by Apache 2 on a Windows 2003 Server.
- It is big.
- It is a legacy of rather unprofessional developers who did not mind about case sensitivity or directory separators.
The desired situation looks like that:
- Everything migrated to Apache 2 under a Linux distribution of yet undecided flavor.
- Endless tons of code without any caring about the case-sensitivity or directory separator character.
I did some research already, but unfortunately did not find anything which would be suitable also for a production environment.
CIOPFS looks nice but is explicitly meant not to be used on production systems. Would you think
mod_spelling for Apache would be an option? The yet unresolved question for me is, if PHP accesses files with help of that module or directly (which would make it useless).
Should we swallow the bitter pill and go through all the code? We would like to avoid that, as we will replace the current software environment piece by piece with new build stuff (in long term).
mod_rewrite) for the legacy application (residing in the old setup) via the new server, replacing the parts this way...maybe.