Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Pretty straight forward… I have just setup a Windows Server 2008 r2 Virtual Machine that will host our company’s Intranet. I use XAMPP locally but was wondering if using XAMPP on this new production server would cause any issues.
Sure, I could install each on my own, but XAMPP makes everything so easy and since it will strictly be viewable to anyone with access to our network (internal only)… what is the harm… if any?
Considering the XAMPP philosophy:
I would say that installing XAMPP on a production server is not a good idea, because all features are turned on and the default configuration is setted to be use by a local server.
You will almost never have any problem using XAMPP on a local server considering that it’s just an easy way to installing/configure Mysql, Php, Perl and Apache. But you must to be sure of what you need to open in your configuration file, for a dev server.
You should so verify XAMPP configuration before.
But since LAMPP 0.9.5, XAMPP installation can be secured by calling »/opt/lampp/lampp security«.
I never test this secured installation.