can I move apache, php and mysql to subfolders?

[microbe]

Hey folks,

I already have Windows users of my application that includes an early version of Uniform Server and would like to move to xampp. (The problem with Uniform Server new version is it uses WAMP which doesn't like a space in folder name e.g. "program files").

My issue with xamp (which works OK) is that existing users have a file structure like this:

Code: Select all

/application/
             /usr/
                 /local/
                       /apache
                       /php
                       /mysql
             /www

is there any way I can move apache, php and mysql into subdirectories instead of having them in the xampp root directory?

Hopefully it is easier than trying to write a patch to shift everyone else to a new file structure without breaking everything

Thanks in advance

[JonB]

(The problem with Uniform Server new version is it uses WAMP which doesn't like a space in folder name e.g. "program files").

Guess what - neither does XAMPP - DON'T INSTALL in "Program Files'. (or do so having been warned) Feel free to search this forum for 'corrections to misconceptions about spaces in file names'.

BTW -- also -- XAMPP is really not developed for production envrironments, its intended to be a development and testing tool.

I am not saying to not convert to XAMPP, just warning you of possible obstacles.

Good Luck with your project.


OSD

[Altrea]

like JonB said: NEVER install XAMPP in a directory with spaces or special chars!

is there any way I can move apache, php and mysql into subdirectories instead of having them in the xampp root directory?

Well, that is the big strength on xampp, that you have all you need in one directory.

It is possible to have all single components of xampp in directorys you want. But if you would have the knowledge for this you wouldn't ask here.

[bwls@earthlink]

If XAMPP is not designed to be a 'production' environment what is the best method to establish a 'production' environment?

Also,
Can an XAMPP installation be used by IIS on the same machine as Apache (of course on different ports)?

Thanks,
Bill

[JonB]

If you don't understand the meaning of a production environment or what constitutes one, I have to ask what it is you are attempting to accomplish?

Hopefully it is easier than trying to write a patch to shift everyone else to a new file structure without breaking everything

Everyone else? Applications? Break, break what??

Code: Select all

/application/
             /usr/
                 /local/
                       /apache
                       /php
                       /mysql
             /www

I would say "that" (having users that are reliant on services) constitues a production envirronment.

read down a bit here:
http://www.head-fi.org/forum/thread/167 ... nment-mean

Also,
Can an XAMPP installation be used by IIS on the same machine as Apache (of course on different ports)?

I can't even guess what you are trying to ask here.

I will directly answer the question about establishing a proper IT-type production environment, nevertheless:

In general - it means properly installing and integrating the correctly scaled components needed to provide a reliable and effective platform.

So in this case, it would mean installing Apache, PHP and MySQL (plus since you seem to want to have users, likely an FTP server) in the correct versions (full installs) on a server OS designed to be used in that role and then configurubng all of them to operate as a whole -- Or you could learn an Open Source provisioning system (probably the 'right answer').

Why do that? Becasue in that scenario, all the 'real products' will operate with their full range of features, and be deployed in the manner suggested by the developers -- which will make getting help reasonably easy.

You are actaully welcome to do anything your heart desires with Open Source software. Just don't plan on things like XAMPP, WAMP and the ilk to become full-scale stand-ins for 'the real thing' (fully installed standalone products properly integrated)

Good Luck with your project.

[microbe]

Thanks for that,

Not that the questions was mine, the answer is important to me.

I suppose my "users" are technically a production environment but let me clarify.

The application is station management software for volunteer firefighters in Australia. Most of the computers are not even connected to the cloud.

It is (obviously) written in PHP and uses mySQL db. I would love to have a standalone app but my skills are web development not Visual Basic or C++ or whatever.

It came about because I wrote this for my brigade not expecting it to be used by others. But members of other brigades inevitably saw it and wanted a copy (as the official service doesn't provide any software) and it has grown from there.

But I cant think of another way of doing this. Essentially I have a PHP/mySQL application that others want to be able to use on standalone computers. I have to distribute it as an installable package that is dead easy to run (which I have handled using Inno installer).

Any thoughts or suggestions?

[JonB]

Yes -

I have to think about it a bit, and I am sure others may chip in -

BUT - with XAMPP, you could build a 'ready to put in place' environment (including the PHP app) for them to run locally - once you had it all 'down'. They would install/setup XAMPP and then 'copy in' your 'package'. For any one group/station, that would proabably work fine (particularly if they really only want to use it locally).

Its a project, but not at all un-doable. XAMPP will actually run on USB drives, and, even after installation, can be ported to another machine fairly easily. I use a thumb drive to take my projects around on.

Good Luck again.



BTW, XAMPP (other than the installer/Control Panel itself) is 100% registry agnostic, so the matters of the Windows registry, 'Program Files', traditional Windows installers and all that associated malarkey can be disposed of in your consideration of methods. Its bascially all ported *nix stuff, and the prohibitions on spaces, special characters in foldernames come from the Unix filesystem and the extensive use of regex's.

[microbe]

Thanks again...I genuinely appreciate you taking the time with your thoughtful responses.

I think the solution is for me to install XAMPP and then use that as the basis for my installation package.

Then I am just going to have to develop nerves of steel and write a patch to move existing user files around

How do you spell aaarrrggghhh!!!?