Last Updated: 29 Oct 2023
|
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
server-tech:macosx:upgrading-mamp-pro [Feb 25, 2018 07:20 AM] dordal |
server-tech:macosx:upgrading-mamp-pro [Oct 29, 2023 08:45 AM] 114.119.141.194 old revision restored (Oct 24, 2023 09:21 PM) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | = Upgrading MAMP Pro = | ||
+ | Upgrading MAMP Pro can be a little complicated. Here's the procedure I used to upgrade from 3 to 4.1: | ||
+ | |||
+ | * If you've customized your '' | ||
+ | * Make sure MAMP isn't running. | ||
+ | * Download the new MAMP from https:// | ||
+ | * Run the installer. It should automatically figure out that you need to upgrade, and do that for you. | ||
+ | * Load MAMP Pro and allow it to initialize its components. | ||
+ | * The new version of MAMP Pro may come with new templates for '' | ||
+ | * **NOTE: As of MAMP 4.X there is a new option 'Make this version of PHP available from the command line' which negates the need to do these manual linking steps.** That said, if you want to manually link your PHP binaries from my ''/ | ||
+ | sudo rm / | ||
+ | sudo rm / | ||
+ | sudo rm / | ||
+ | sudo rm / | ||
+ | sudo ln -s / | ||
+ | sudo ln -s / | ||
+ | sudo ln -s / | ||
+ | sudo ln -s / | ||
+ | </ | ||
+ | * MAMP very annoying uses a different php.ini if you call it on the command line vs. calling it via apache. So I typically link the command line over to reference the apache one: < | ||
+ | sudo ln -s "/ | ||
+ | * You'll probably want to link '' | ||
+ | sudo ln -s / | ||
+ | </ | ||
+ | * You may need to [[installing-phpunit-on-mamp|reinstall phpunit]] or other software you've customized MAMP with. | ||
+ | * That should be it. Test your sites out and see if they work. |