For some strange reason the Applications folder for a user login has changed itself.
It seems to have created an Alias for the real Applications folder and then stuck in Chrome Apps.locaslized in the original folder of applications.
This means I can no longer access my applications via the terminal. This is inconvient as I edit the Vhosts file of MAMP this way.
Can anyone shed some light as to how this might have happened and how I can revert it back so that Applications are put back into the applications folder as they should be
I have added an image so u can see what I mean
Type in:
cd /Applications
It will take you back to your list of all apps. I don't have an explanation but after playing around with the same issue I got back to my apps folder like that.
I'm having this same problem and this is the only other instance of it I found on google. Has anyone else encountered this or found a fix? After installing MAMP my Applications folder is now at /Applications instead of /Users/[username]/Applications
/Users/[username]/Applications now only contains Chrome Apps.localized
Related
I am using MacBook Air. I installed the xampp but it's not working.
After some research, I found the URL http://localhost:8080/dashboard/ and I am getting the xampp. Now I am confused where should I get htdocs folder to add my code. Can anyone assist me?
Let's talk about in details
I downloaded the xampp from this link https://www.apachefriends.org/download.html
and I move it on the application. Now I am getting the xampp icon in application.
Then I open the xampp and I got a popup like and I click on start
I enable the 8080 port number.
Then I just I checked in the browser http://localhost:8080/dashboard/ and I found the xampp dashboard page.
Now I am not getting the htdocs folder. would you help me out in this?
I too have had lots of confusion setting up XAMPP on my Mac.
Things the docs said would work, just plain did not.
The short answer to your question: In MacOS X the htdocs dir of the virtual server is in:
/Users/<YOUR-USER-NAME>/.bitnami/stackman/machines/xampp/volumes/root/htdocs
More complete instructions for getting the server up:
Open up the XAMPP Application
Under General/Services start the XAMPP services
Under Network make sure to enable a port config (I chose localhost:8080->80)
In the Volumes "tab" click "Mount" beside /opt/lampp and then you can click "Explore" to open a finder window to the virtual server.
This will cause the virtual Network-Drive 192.168.xxx.yyy to show up in the Finder sidebar which has a single folder named lampp
Additionally a new external drive named lampp will also be available in Finder.
However you get to lampp, put your source-files in the htdocs folder.
Links that DID work for me on first launching:
http://localhost:8080/dashboard/
http://localhost:8080/phpmyadmin/
http://192.168.64.2/dashboard/
Links that did NOT work, in spite of docs claiming otherwise:
http://localhost/ or http://localhost/index.php
http://192.168.64.2/phpmyadmin/ <--Access Forbidden 403
A little late to the thread but I hit and solved this issue and I believe the OP had downloaded and installed the wrong version. At the time I am writing this, the link on the downloads page is for .dmg file is a VM file, or at least missing features of the full download. Instead of downloading that, go to the more downloads section
Once there, choose the version you need for your OS. This, and some mysql tweaks that are answered in multiple connected topics got me running.
Your XAMPP is working fine. You have to use Finder to go to htdocs.
Follow these steps -
Open the XAMPP application and hit "Start" button.
Make sure everything is proper by hitting "Go to Application".
Now you should see the dashboard on your browser, if not, restart the application and try again.
Go to Finder and on the sidebar you should see a volume labeled "192.168.64.2", go there and you will find a folder named "lamp".
See under the locations section
Inside lamp there will be htdocs, where you can place all the files you want the browser to access.Click on lamp
To start off yes I know that this question is among many others on this site, but it seems that none of the other answers are working for me. Here is what has happened...
I originally had the Xcode file in its own folder in my documents, then I moved it onto an external hard drive, along with all my other files, and then wiped my hard drive. I can build the app but not run it on the simulator on on my device, and the last thing the little status bar at the top says is "signing product" So... just looking at other responses could this be because of me not having the "original" files? Thank you in advance for any help!
Oh a side note, I have the app on the app store, before it all went in the toilet, I don't know if that helps in any way. I have tried everything under the sun from changing the bundle identifier, getting new certificates, repairing permissions with disk utility, and clicking "ignore user permissions" on my external drive.
select info
Enter Bundle name As : ${PRODUCT_NAME}
Executable file : ${EXECUTABLE_NAME}
I want to make my application autorun, like using autorun.inf on Windows. I googled and there is one way for me to do that:
"On the Mac side there are many applications you can buy for creating a Finder window that looks a certain way but all these changes can be made within finder. You then will need to copy the DS_Store file to the CD and finder will automatically apply any changes that you have made.
Also using -hfs-openfolder will cause it to open automatically when inserted on the mac."
Can anyone tell me more clearly about that, or is there any other way?
Thanks so much.
According to this page, you should be able to do that with bless:
sudo bless --folder "/Volumes/discName" --openfolder "/Volumes/discName"
The man page confirms that, at least on 10.6.8. I don't have Lion in front of me right now.
I am wondering how an application like appzapper can detect the files related to an application?
All ideas are welcome.
Thanks for your help,
Regards,
By looking into the standard locations that usually are used by applications to store preferences (like Library/Preferences/ , Library/Caches, etc., both in your home directory ~/ and under / ) I couldn´t find any file or folder that isn´t using either the applications name (eg. ~/Library/Application Support/Firefox) or it´s bundle identifier (eg. ~/Library/Preferences/org.mozilla.firefox.plist) in its name; so I guess they´re just using that.
In the case of AppZapper you can go ahead and try for any (not currently running) Application to rename the ~/Library/Application Support/AppName folder for example to ~/Library/Application Support/111AppName - AppZapper doesn´t find it anymore. If you change it to ~/Library/Application Support/AppName111 it shows up as a related file.
Out of this you can conclude that there isn´t any magical linkage between a folder full of preferences and it´s associated application that AppZapper is reading out, it´s merely checking for folders starting with the Application´s Name.
I'm using Mac Snow Lepord and can't find "~/.config/MonoDevelop/" for the life of me. I have MonoDevelop (v2.2.2) up and running already, but when I tried to set up a template the IDE started having problems.
Namely, whenever I went to Monodevelop -> preferences-> Code Templates I would get an error saying "Argument cannont be null".
I tried removing MonoDevelop from my Mac and re-installing but that doesn't appear to fix this problem so I thought if I could find the above folder maybe I could remove that. However I am not sure how to find it. I put the address directly into Mac's "finder" search box and no results were returned.
Can anyone help?
Note: You are not going to see your .config directory in your user directory in finder unless you show hidden files. You are going to have to get there via bash in the Terminal.
The tidle ~ would normaly expand to your home directory, e.g. ~/foo.txt is /path/to/your_directory/foo.txt, depending on where 'home' is on any given system.
So, the file you are looking for is /Users/your_username/.config/MonoDevelop/ ...
Also, there are some shells / systems that simply do not support tidle expansion.
Since you are on a Mac, you'll actually have to go to ~/Library/Prefernces/MonoDevelop-2.x to do your install.