What would be the best way to get off of XAMPP?
Posted: Fri Oct 13, 2017 11:38 pm
I'm using Mac OS X 10.12.6
I have 55 local copies of live projects running in my XAMPP based localhost.
Each has thier own www.foobar.xamp local domain name in the hosts file. There are other projects I have not set up a local domain for.
Some of them are older, current, and in-progress versions of the same project and I need to be able to visit them simultaneously at their local domain instead of swapping them in and out of a single port number like http://localhost:8080
Over a dozen of them use the same core php files and when testing for bugs in one I need to be able to quickly open at least 6 other projects to test the same bug or bugfix in all of those as well.
My php version is 5.5.19 because it is the closest version I could find to the versions in use on the live servers where most of the projects live. Those live servers use: 5.3.15, 5.3.26, 5.4.44. It is very likely that those servers will never be upgraded.
Three projects are on a server using 5.6.31. It is possible that 3 more will be moved to that server next year. It is also possible that at least 1 project next year will be migrated to a php7 server and another one built from scratch on a php7 server. But at the moment 90% of my income is from maintaining old projects on these old servers.
I want to start using modern tools like composer and npm and homebrew cask. But the very old version of XAMPP I have installed at the moment has added something to my terminal environment named HEAD that is definitely not the HEAD script that many other terminal things like homebrew expect.
There are other problems I've encountered that are probably also the fault of XAMPP. For example: https://github.com/composer/composer/is ... t-69469119
And I couldn't tell you the last time I successfully updated or installed anything using Homebrew.
So to avoid these kinds of problem entirely I'd like to completely remove XAMPP from my OSX terminal environment, but I do not know the best way to replace it with something that would allow me to just as easily run all projects simultaneously with their own local domain name. I also think it would be best if I could somehow stick to an older version of php or preferably the exact same php version used by the live servers most of these projects live on.
I have not updated to the latest version of OSX yet because I heard there was a problem with it an Laravel Homestead and I was considering trying to move all of the projects into a Homestead VM.
The thing I don't like about my experience with Homestead so far is that I've accidentally destroyed the VM on multiple occassions without first remembering to export all of my databases. I think I would have to set up a 2nd VM that I never destroy in which to store all my databases and then modify the local env config of every project to connect to that VM's mysql service when running locally. The thought of doing that depresses me.
Can you give me any advice?
I have 55 local copies of live projects running in my XAMPP based localhost.
Each has thier own www.foobar.xamp local domain name in the hosts file. There are other projects I have not set up a local domain for.
Some of them are older, current, and in-progress versions of the same project and I need to be able to visit them simultaneously at their local domain instead of swapping them in and out of a single port number like http://localhost:8080
Over a dozen of them use the same core php files and when testing for bugs in one I need to be able to quickly open at least 6 other projects to test the same bug or bugfix in all of those as well.
My php version is 5.5.19 because it is the closest version I could find to the versions in use on the live servers where most of the projects live. Those live servers use: 5.3.15, 5.3.26, 5.4.44. It is very likely that those servers will never be upgraded.
Three projects are on a server using 5.6.31. It is possible that 3 more will be moved to that server next year. It is also possible that at least 1 project next year will be migrated to a php7 server and another one built from scratch on a php7 server. But at the moment 90% of my income is from maintaining old projects on these old servers.
I want to start using modern tools like composer and npm and homebrew cask. But the very old version of XAMPP I have installed at the moment has added something to my terminal environment named HEAD that is definitely not the HEAD script that many other terminal things like homebrew expect.
There are other problems I've encountered that are probably also the fault of XAMPP. For example: https://github.com/composer/composer/is ... t-69469119
And I couldn't tell you the last time I successfully updated or installed anything using Homebrew.
So to avoid these kinds of problem entirely I'd like to completely remove XAMPP from my OSX terminal environment, but I do not know the best way to replace it with something that would allow me to just as easily run all projects simultaneously with their own local domain name. I also think it would be best if I could somehow stick to an older version of php or preferably the exact same php version used by the live servers most of these projects live on.
I have not updated to the latest version of OSX yet because I heard there was a problem with it an Laravel Homestead and I was considering trying to move all of the projects into a Homestead VM.
The thing I don't like about my experience with Homestead so far is that I've accidentally destroyed the VM on multiple occassions without first remembering to export all of my databases. I think I would have to set up a 2nd VM that I never destroy in which to store all my databases and then modify the local env config of every project to connect to that VM's mysql service when running locally. The thought of doing that depresses me.
Can you give me any advice?