跳到主要內容

Install and configure Apache, MySQL, PHP and phpMyAdmin on OSX 10.8 Mountain Lion [I]

Get your Local Web Development Server Purring on all Fours

With the new cat out of the bag, getting the AMP stack running is a little different on OS X Mountain Lion 10.8 than is its predecessor OS X 10.7 Lion, here is the lowdown on getting Apache, MySQL, PHP and phpMyAdmin running on the new Apple operating system. (OSX 10.7 AMP guide is here).
If you have upgraded from a previous OS X your hosting environment will be whacked and you need to fix certain configuration files to get that environment back, in particular enabling PHP, and if you used the username/Sites document root folder in your home account you will need to add back in a user configuration file.
Apache/WebSharing

The first difference in the new OS X 10.8 is the dropping of the GUI option in System Preferences > Sharing to turn onWeb Sharing, it may be gone but the webserverApache is definitely under the hood of the OS and ready to go.


No Web Sharing Option in System Preferences
Apache is pre-installed in the OS and needs to be enabled via the command line - this needs to be done in Terminal which is found at /Applications/Utilities/Terminal
to start it

sudo apachectl startto stop it

sudo apachectl stopto restart it

sudo apachectl restartTo find the Apache version

httpd -vThe version installed in Mountain Lion is Apache/2.2.22

After starting Apache - test to see if the webserver is working in the browser -http://localhost - you should see the "It Works!" text.
If you want a GUI point and click web sharing toggle switch in System Preferences, this is one from clickontyler. Some people have had issues with this sys pref so use at your own decision.
Document Root

Document root is the location where the files are shared from the file system and is similar to the traditional names of 'public_html' and 'htdocs', OSX has historically had 2 web roots one at a system level and one at a user level - you can set both up or just run with one, the user level one allows multiple acounts to have their own web root whilst the system one is global for all users. It seems there is less effort from Apple in continuing with the user level one but it still can be set up with a couple of extra tweaks.
System Level Web Root

- the default system document root is still found at - 

http://localhost/The files are shared in the filing system at - 

/Library/WebServer/Documents/User Level Root

Interestingly the user document root level is missing the '~/Sites' folder in the User account on a clean installation, you need to make a "Sites" folder at the root level of your account and then it will work. Upgrading from a previous OS X version preserves the Sites folder but removes the ability to web serve from it - this is where you need to add in a 'username.conf' file.
Create a Sites folder at the account root level 
Check that you have a “username.conf” filed under:

/etc/apache2/users/If you don’t (very likely), then create one named by the short username of the account with the suffix.conf, it's location and permissions/ownership is best tackled by using the Terminal, the text editor 'nano' would be the best to deal with this. 
Launch Terminal, (Applications/Utilities), and follow the commands below, first one gets you to the right spot, 2nd one cracks open the text editor on the command line (swap 'username' with your account's shortname, if you don't know your account shortname type 'whoami' the Terminal prompt):

cd /etc/apache2/users
sudo nano username.confThen add the content below swapping in your 'username' in the code below:

<Directory "/Users/username/Sites/">Options Indexes MultiViewsAllowOverride AllOrder allow,denyAllow from all</Directory>Permissions on the file should be:

-rw-r--r-- 1 root wheel 298 Jun 28 16:47 username.confIf not you need to change...

sudo chmod 644 username.confRestart Apache for the new file to be read:

sudo apachectl restartThen this user level document root will be viewable at:

http://localhost/~username/

這個網誌中的熱門文章

正確設置404頁面及其他.505,500....

正確設置404頁面 404頁面的設置是否正確直接關係到網站粘性,而現在很多網站的錯誤頁面返回碼都是200和302,只要蜘蛛爬行錯誤頁面不是404,那麼你的404頁 面設置就是錯誤的了,這裡跟大家介紹如何正確設置404頁面。 怎麼正確設置404頁面?很多人看到這個話題可能覺得下文不屑一顧,其實你是否知道自己的404頁面有沒有設置正確呢?很多開源的cms系統和博客 系統都會帶有404頁面,你是不是覺得這樣已經ok了?不用設置了?這些想法是錯誤的,我們做優化的時候,應該測試404頁面時候生效,設置是否正 確等。下面我們詳細說明怎麼設置404頁面。 這先說一下怎麼樣的404頁面才是有效的404頁面。大家應該都知道搜索引擎是通過http狀態碼來識別網頁狀態的,那麼當蜘蛛檢索到一個錯誤鏈 接時,就需要返回404狀態碼來告訴搜索引擎,這個頁面是錯誤頁面,以後不用索取了。而如果返回200,則告訴搜索引擎這個頁面是正常頁面。 所以我們要查看網站錯誤頁面的返回碼是200還是404,而現在很多網站的404頁面返回碼是200而不是404.    那怎麼正確設置404頁面?

Mac OS X Server 架設兩個網站、兩個郵件伺服器

from:http://www.bnw.com.tw/conference/viewtopic.php?t=208 我的需求要更簡單。  朋友的工作室就兩三人而已,另外一個工作室也是兩三人。  希望有屬於自己的網站及網域名稱郵件  www.123.com   abc@123.com  

無法在Mac Os X 中移動、解除鎖定、修改或複製項目

您可能無法移動、複製或拖移項目。您可能無法解除鎖定一些項目。 秘訣 :如需刪除檔案與清空垃圾桶的說明,請另外參閲 無法清空垃圾桶或將檔案移至垃圾桶 。 本文件的主題屬於兩大常見問題之一。 秘訣 :有時無法從某個位置移動項目或將項目移至某個位置是正常的。Mac OS X 會限制某些檔案夾 (包括應用程式、程式庫以及系統) 的存取,以保持作業系統和使用者資料的完整性。 問題 1 如果您在 Mac OS X 10.2 或以上版本中試著移動檔案,然後出現訊息:「因為項目 (項目名稱) 已鎖定,所以無法完成此作業。」 如果您試著修改項目的權限,可能會出現訊息:「無法完成此作業,發生無法預期的錯誤 (錯誤碼 1)。」 如果您將一個卷宗拷貝成另一個卷宗,例如將卷宗的圖像拖移至另一個圖像上,或拖移至其所有的視窗之一,就可能會發生此問題。 問題 2 出現包含下列訊息之一的提示框: