I've got an issue where if I upgrade MAMP, it generates a new folder in my Applications folder. So far this has occurred three times now and I'm no closer to finding out why it's happening.
Here's a screenshot of the Finder window showing all MAMP folders. The ones that got created after updating MAMP all have the dates and times they were created.
I've tried deleting the new folders and leaving the original one but that prevents MAMP from opening ("These files are in the trash") but the path for the document root still points to the original folder. Here's a screenshot of that:
Can anyone advise on how best to remove these duplicates and prevent this from happening again? Each duplicated folder adds at least 10GB to my storage and I'm running low! I can't find any reference to this in MAMP's documentation, or even on this site.
Any ideas?
Thanks!
As Peter pointed out that is normal behaviour. The folders containing dates (MAMP_2018-0....) are the backups of the previous installations/versions. The following named folders always contain the latest updated installation files:
MAMP
MAMP Pro
It is advisable NOT to store development sites in the MAMP/htdocs directory. It is advisable to set the Document Root to a separate development directory (not within the MAMP program folder) e.g. DevServer under My Docs.
Before MAMP/MAMP Pro is upgraded record the preference settings. Next upgrade the software and recheck the settings match after the upgrade. Then launch and check your development website(s).
I've experienced this when upgrading in the past. I believe this is normal behaviour.
I have just gotten into the habit of deleting the old ones and haven't had any problems.
Related
I migrated my Mac to another Mac and after doing so I changed the user directory name. This has already caused many issues in other applications but I haven't been able to solve the code issue.
The problem:
Every time I open a new instance of vscode it opens with no installed extensions at all despite having installed many.
I am not very familiar with Mac yet and I have tried removing the App and redownloading as well as deleting some files from the ~/Library folder (cookies, preferences).
I have found the issue on Github with a workaround at the bottom of the issue:
https://github.com/microsoft/vscode/issues/168579
Basically, every new extension installed correctly but in the extensions.json file the path was wrong. It was looking for the extension in the wrong user directory (the old one before migrating).
Just switched to a new MacBook after my old one got a logic board issue and died. I transferred some apps over from an external hard drive, and none of them will run-- I just get the error in the title.
This has been addressed before, but none of the solutions have worked. I've tried:
Manually setting file permissions
Cleaning the project multiple times
Setting the compiler for C/C++/Obj C to default
Restarting my computer
Replacing my info.plist file with a clean one
Deleting derived data
Checked my architecture settings are accurate
Some other solutions I've found on here (deleting folders that code was moved into, etc) aren't applicable
Worth noting that in addition to switching computers I upgraded Xcode to the latest version (my version on the previous computer was about a year old).
Does anyone have any other thoughts? I'm stuck and have no idea what else to try.
Try change permissions recursively. Go to terminal, open folder with your project and write:
sudo chown -R $USER .
I'm using Windows 10 and run various Sf projects on various versions of Symfony from 2.3 to 3.2. I've had these problems in all of them since forever (also on Win 7). In some projects it's permanent, in others incidental - when clearing cache, things go bonkers - sometimes it can't rename a directory, sometimes it can't delete a file, sometimes it can't open one. Examples:
[Symfony\Component\Debug\Exception\ContextErrorException] Warning: file_put_contents(H:\_Moje_dydy\Documents\Projekty\atm\src/var/cache/dev/classes.map): failed to open stream: Permission denied
This one is very common (but only in some projects!):
[Symfony\Component\Filesystem\Exception\IOException] Cannot rename "H:\_Moje_dydy\Documents\Projekty\friendly_score\src_rainfin\app\cache\de_" to "H:\_Moje_dydy\Documents\Projekty\friendly_score\src_rainfin\app\cache\dev".
In some cases, complete wiping of the cache dir with admin rights helps. In some, it doesn't, and in some other cases it's completely impossible (deleting the dir's contents). Many times, when I was unable to delete the directory and looked into NTFS permissions on some folders within the cache directory I saw complete chaos like this:
Note repeated records for same users, multiple "special" rights (they have very weird sets of permissions within them, that often contradict one another).
In some "heavier" cases it not only interfered with the cache:clear command but also broke the application altogether. In most of those cases it needed very deep interventions to enable me to simply delete the cache dir (some subdirectories had so crazy permissions that even as admin user I was unable to delete them and had to mingle with permissions first).
Here's what I'm using right now:
Windows 10 (happened on Windows 7 too);
XAMPP with PHP 7.1 and Apache 2.4 (happened on older versions with PHP 5.6 and 5.4 too);
Netbeans 8.2 as IDE (happened with previous versions too);
cygwin to run CLI commands;
git.
My primary question is: what mingles with those permissions in such a crazy way? Apache+PHP while creating cache on runtime? Netbeans, even though it ignores cache and log dirs (theoretically - I haven't specifically put them to ignore list in NB)? Git, even those these dirs are ignored in each repo (rather improbable)? Me, while running CLI commands via cygwin (also rather improbable)?
I've been battling it for a long time to no avail...
Do you guys have any insights on this? Thanks.
i had similar problems....
Until i switched from xampp to laragon
I know that sounds odd ,but in my case it solved all the problems.
Symfony provides a documentation about these permission problems :
http://symfony.com/doc/current/setup/file_permissions.html
You can do either use umask(002) before you whole application, or set ACL.
ACL and umask both set a default access right for all new files.
I'm thinking of hosting WordPress on my Dropbox folder for development work. Has anyone tried this?
I'm wondering if there's a way to keep XAMPP on your local machine but direct the root to the Dropbox folder.
First of all, both WordPress and XAMPP produces a lot of garbage files (logs, PIDs, configs, sessions) etc. that will simply trashout your Dropbox. I'm pretty sure about that, because I tried to version XAMPP on SVN, which is pretty the same as SVN, and got really tired on searching more and more folders that should be ignored (non-versioned) because of containing data and other temp files.
And for answering your question. Sure thing, you can. After installing XAMPP (preferably outside Dropbox), go to "xampp\apache\conf" folder, edit "httpd.conf" file and change the value "DocumentRoot" variable (around line 90) to whatever you need. You may need to use ".." for specifying parent folder many times, if your Dropbox is outside XAMPP folder.
I won't discuss security matters here, as you should know, that such solution is highly risky and on the other side of security topics.
For reasons that we won't discuss, I have determined that MAMP is a pile of crap that haunts my system, and unless I remove it fully, I will live in shame.
I've done the obvious thing and removed the MAMP directory from my Applications folder, however, I don't like wandering files, and I have an itching feeling that MAMP put some .sock files somewhere, or otherwise made a mess in my file system.
What files does MAMP add to a system when it's installed, and where are they?
If you have proof that MAMP doesn't actually put files anywhere (besides the /MAMP dir), then that's as good an answer as any!
From their help page:
To "uninstall" MAMP, you only have to
delete the MAMP directory and
everything returns to the original
state (MAMP does not alter anything on
the "normal" OS X).
When you download MAMP, you get a MAMP Pro trial, also. In the MAMP Pro folder, there is an 'uninstaller'. When you open the uninstaller, it asks you if you would like to remove all traces (preferences, etc.)
When I used it, it appeared to delete absolutely everything for MAMP and MAMP Pro.
MAMP does alter one system file: /etc/hosts (it adds any virtual hosts you may have created under the "hosts" tab here).
You may want to delete those entries.
To do so, go to Finder, select "Go"-"Folder" from the menu, and enter "/etc". Then you need to temporarily change permissions on both the host file and the directory it's in, by right clicking and chosing "Get info" and changing the permissions.
You can then edit the hosts file in Textedit.
After you're done, you should put the permissions back to what they were to be on the safe side.
AppZapper is a great tool that solves this problem. Search Google for it, it's free for the first 5 time you use it.
To fully uninstall any application. Try installing AppTrap. + it's free
Each time you move an application to Trash, AppTrap would find the preference files in your library and let you delete them as well.