losthost SVN repository and php testing configuration
Posted: Mon Sep 18, 2006 10:55 pm
I am a little confused about what I should do about a configuration I am attempting to arrange for my laptop, which is used primarily for writing and testing code.
I have some requirements and some assumptions with regard to the problem, and some questions to answer that stem from them. I am also learning about this stuff and somewhat of a noob.
Requirements:
- host a subversion repository locally.
- whether via a separate instance of apache (or via a configuration of apache2 that is more suitable to these aims), host a webserver locally that can be used for testing and development of PHP for now, and later for perl, etc.
- I already have svn up and running on apache 2 ssl and unless avoidable, I'd like not to have to rebuild that.
Assumptions:
- subversion requires apache 2
- subversion requires, at minimum, a self-signed ssl cert.
- apache 2 is considered by many unreliable for a production environment and therefore less suitable for a development environment, whereas most webservers still run apache 1.3.
- php does not support threading.
- "php-cgi" by which I assume to mean the cgi interface for php may support threading or work somehow in compatibility with the threaded apache2???
Questions:
- does subversion require that threading be enabled in the apache build?
- would an apache2-based testing environment be best considering that an app under development may ultimately be deployed on apache1.3 indefinitly.
- could I benefit from having an instance of apache 1.3 operating on another port?
- would "php-cgi" be better than a separate instance of apache and why?
I have been somewhat stymied by this problem.
Thanks, and sorry for the longwindedness.
I have some requirements and some assumptions with regard to the problem, and some questions to answer that stem from them. I am also learning about this stuff and somewhat of a noob.
Requirements:
- host a subversion repository locally.
- whether via a separate instance of apache (or via a configuration of apache2 that is more suitable to these aims), host a webserver locally that can be used for testing and development of PHP for now, and later for perl, etc.
- I already have svn up and running on apache 2 ssl and unless avoidable, I'd like not to have to rebuild that.
Assumptions:
- subversion requires apache 2
- subversion requires, at minimum, a self-signed ssl cert.
- apache 2 is considered by many unreliable for a production environment and therefore less suitable for a development environment, whereas most webservers still run apache 1.3.
- php does not support threading.
- "php-cgi" by which I assume to mean the cgi interface for php may support threading or work somehow in compatibility with the threaded apache2???
Questions:
- does subversion require that threading be enabled in the apache build?
- would an apache2-based testing environment be best considering that an app under development may ultimately be deployed on apache1.3 indefinitly.
- could I benefit from having an instance of apache 1.3 operating on another port?
- would "php-cgi" be better than a separate instance of apache and why?
I have been somewhat stymied by this problem.
Thanks, and sorry for the longwindedness.