Please vote for it is you think this functionality is important. Add an options allowing the user to decide if Local’s servers should start on system boot.ĮDIT: I have made a feature request.Add a “start/stop servers” button inside the application.I humbly request that Local’s developers: (Again, change “username” to your macOS username). Sudo nohup /Applications/Local.app/Contents/Resources/extraResources/lightning-services/nginx-1.16.0+3/bin/darwin/sbin/nginx -c "/Users/username/Library/Application Support/Local/run/router/nginx/conf/nf" -p "/Users/username/Library/Application Support/Local/run/router/nginx" -g "user root staff " & However, you will need to manually restart Local’s NGINX server if you want to use Local again (or reboot your computer, ugh): system user that PHP runs at (such as www-data if you are running with Apache) can create and write to the file. And note that the path to NGINX might change in future versions of Local).Īfter issuing that command NGINX will gracefully shutdown, and ports 80 and 443 become available. (You will need to change “username” to your macOS username. But if you were creating a Rails site, it’s likely more setup would need to be done. There is a good chance that you have an instance of mysql running and you have to find it and hit quit process. WordPress runs on even PHP4 and simply needs MySQL. Solution 1 Just in case anyone is having the same problem, here is how I fixed it: I opened the Activity Monitor program and selected 'All Processes' Next I search for 'mysqld' in the search text field. Sudo /Applications/Local.app/Contents/Resources/extraResources/lightning-services/nginx-1.16.0+3/bin/darwin/sbin/nginx -c "/Users/username/Library/Application Support/Local/run/router/nginx/conf/nf" -p "/Users/username/Library/Application Support/Local/run/router/nginx" -s stop JA few things I didn’t discuss in the video: Make sure new live web server has the same technologies available as you do locally. Just go to MAMP > Preferences > Ports Tab and click the Set to default Apache and MySQL.
#MAMP PRO PORT 80 APACHE CONFLICT FREE#
In addition, Local has a launch daemon that starts NGINX on system boot, which means even if you haven’t started Local, it hijacks the ports anyway.Ĭurrently if you want to free up those ports you need to kill Local’s NGINX processes. Now you should be able to use port 80 (and almost any other) in MAMP. Local has no such button, so once NGINX is running there is no GUI to stop it, and thereby free up ports for MAMPs servers. I setup MAMP Pro to use the default ports for Apache (80) and MySQL (3306). The difference is that in MAMP there is a big button labelled “Servers”, which will stop and start the servers. MAMP will restart itself with the new default ports configured. Click on Set to default Apache and MySQL ports. Like Local, the servers will continue to run after the MAMP application is closed. This settings adjustment in MAMP is simple: Open up MAMP and hit the Preferences button. When the MAMP front-end application is launched, it starts the servers (NGINX/Apache/MySQL/etc.). Here’s how MAMPs servers work, for comparison: In my case, I want to run MAMP Pro and Local side by side. It makes it difficult to use Local alongside another server.
0 kommentar(er)
