Posts tagged ‘Mac’
I use MAMP daily. I love MAMP. I recently discovered how truly awesome MAMP Pro is too. But that’s a story for another time. I recently upgraded from MAMP 1.8.4 to 1.9. When I got MAMP 1.9 installed I started the servers. Apache came up but MySQL didn’t want to. I tried shutting down both servers and starting it back up again, which didn’t work.
Thankfully, there is a pretty simple fix. To begin with, make sure MAMP is shut down. Next, open Terminal. To open Terminal either open Spotlight (Cmd+Space) and type “terminal” or you can find Terminal in the /Applications/Utilities/ folder.
Once you get Terminal opened, type the following:
ps aux | grep mysql lsof -i killall -9 mysqld
That’s it. Start up MAMP and MySQL will come back up just like normal. Another option would be to simply change the port number MySQL is using in MAMP. Restarting your computer may work too but I did’t try that.
I guess I never noticed it, but I have a lot of menu icons! In order from left to right is:
Adium
Waveboard
Tweetie
BetterTouchTool
Alfred
Dropbox
Google Notifier – Calendar
Google Notifier – GMail
Caffeine
MobileMe Sync
Time Machine
Bluetooth
Wireless
Audio/Volume
Time
Spotlight
Check out a screenshot of all of them on my desktop:
After almost a month without a laptop, I finally got one again. You’d be surprised how much wish you had a laptop when don’t have one. It is a 15″ Macbook Pro. 2.66 GHz processor. 4Gb RAM.
Now I get to go through and install all of the software and set up all of my preferences.
My home command center is almost complete!
This took me three days to figure out so hopefully this saves someone else a little bit of time.
The most common use of .htaccess files is removing file extensions, such as index.php, from a website URL. They are much ore powerful than that though. I’m not going to go into the details about what .htaccess files can do, shouldn’t be used for, best practices, or anything else like that. I’m going to show you how to get .htaccess files set up and working with MAMP.
The only requirements are that you have a Mac (that’s the first ‘M’ in MAMP) and the MAMP software already installed. I am using the latest version. MAMP will install everything else you need (Apache, MySQL, and PHP which is ‘AMP’ in MAMP) to get up and running so you can start making your own sites locally.
First and foremost, the location of your website files in MAMP need to go in /Applications/MAMP/htdocs/ That may sound like common sense but that’s what took the longest for me to figure out. I had my files in /Applications/MAMP/bin/mamp/ which is where all of the files for the start page is located. I just made a folder inside there and was going to the site at http://localhost:8888/MAMP/myfolder No matter what I did, the .htaccess file would not work at all from within that directory. So make sure your websites files are in /Applications/MAMP/htdocs/ or a folder within.
The next thing you need to know is ‘htaccess’ isn’t the file extension and there isn’t a file name on the file. The dot at the front typically means it is a hidden file on Unix based operating systems (which the Mac is). So you will need to show the hidden files on your machine. There are a few ways to do this. One of the easiest ways is to use a Dashboard widget. Hidden Files Widget is a great widget for this. If the hidden files are hidden, the button will say ‘Show’. If the hidden files are visible, the button will say ‘Hide’. It can’t get any more simple that that. Install the widget then click the ‘Show’ button. Sometimes the desktop icons won’t come back automatically. If they don’t come back after a minute, click on the Finder icon in the dock and they should come back. Now, go to wherever your website files are located. If there is a .htaccess file in the folder, skip the next paragraph. If it is not there, read the next paragraph.
Here is the catch. It’s tough to create a .htaccess file because the Mac thinks ‘htaccess’ is the file extension but you didn’t give the file a name. So it won’t just let you do it. Wordpress creates a .htaccess file for you when you set up a blog locally. I believe Drupal does the same thing but I’m not 100% positive on that. Other applications possibly do as well. If you aren’t installing a CMS like that, you can always create a custom one and download it. Below is a very basic example of a .htaccess file that I typically use. Once you have a .htaccess file, put it in the root of where your website will live.
The .htaccess file can be opened with TextEdit. You can open it with Dreamweaver or almost anything you want. Here is an example of a typical .htaccess file
1 2 3 4 5 6 7 8 9 10 11 | # BEGIN My_Website <IfModule mod_rewrite.c> RewriteEngine On #RewriteBase / RewriteBase /mywebsite/ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] #RewriteRule ^(.*)$ /index.php/$1 [L] </IfModule> # END My_Website |
The hash marks (#) are comments. I’ll talk a little about the second and third commenta in a second.
If you are developing a site locally, your files may not be in the root of the /Applications/MAMP/htdocs/ folder since you may be working on more than one website. That is what the RewriteBase is for. It specifies where the root of your website is in accordance with the root of the domain or local root. In this example, my website and it’s files are in a folder called mywebsite which is inside my /Applications/MAMP/htdocs/ folder. Since /Applications/MAMP/htdocs/ is my root folder, I don’t have to put that in the path. I just have to put the path from the root folder. If you notice, on the line above that (line 4), I have commented out that line with a hash. When you upload the files to your website, uncomment this line (line 4) and comment out the line after it (line 5). That way the .htaccess file works when you get it on the actual site. If you are not uploading the files to the root of your website, set the path accordingly.
The third comment (line 9) is a variation of the line above it (line 8). Both work pretty much the same. You don’t have to have the first and last comment lines. You can delete them and it won’t effect anything.
That is literally all I had to do to get the site working. I saw sites that wanted me to edit httpd.conf files and php.ini files and all kinds of files under the sun. I didn’t have to though. If you do need to mess with those files, there are a couple pretty good walkthroughs to help you out here and here.
I don’t really want to go into all of the details, but about a month ago my apartment was broken into. They got a lot of my computer equipment. They also left a lot of it behind. They did take both of my computers though. How long is 2 1/2 weeks for a web developer without computer? It’s a lifetime. Time passes very slow.
Thank God I had renters insurance. For $7 a month, it’s almost dumb not to have it. It’s the price of eating at a fast food restaurant. Skip the fast food for one day out of the month and you just paid your renters insurance.
When I finally got the check from insurance, I went to replace my Macbook Pro with another Macbook Pro. No one seems to have any. Well, people have the 17″ but I wanted the 15″. So I have to hold off on get the Macbook Pro. So I started looking at computers to replace a Sony Vaio that was also taken. The only reason I use a PC is to test things in IE, so I wasn’t looking for anything fancy. Then it hit me. Why get a computer that I really won’t use much? I can always get another Mac. Install Windows on a virtual machine or Bootcamp it. This allows me to get a computer I want but still be able to test things in IE. So I got a Mac Mini.
For now it is in my bedroom because it is the only computer I have. When I am able to get another Macbook Pro, I’ll put the Mini in the living room and hook it up to the television. The Mini will by my entertainment computer with light IE testing. The Macbook Pro will be my primary computer.
[Update @8:00PM Feb 21, 2010] And a picture of the Mini on my desk.
