I have been using Coda and regular version of Mamp for local development for longtime without getting into this permission mess. I recently, upgraded to Mamp Pro and setup it with VHosts. I have a site example.com with it's root path set to /Users/john/Sites/example. I have set the owner and group to www in Mamp Pro.
The moment I got all this configured I started having problems with Coda. It keeps asking me the username and password to edit the local files at /Users/john/Sites/example. I guess I have to enable FTP on my Mac and then add a site in Coda to stop it asking me to enter username password for every single file. However, I have no idea on how to get this working. I am using Lion 10.7.2
Additionally, I have setup etc/hosts file for pointing example.com to 127.0.0.1
UPDATE: Though the accepted answer by #mini does not directly answer this question. It is still an elegant solution with seamless integration with Coda.
Consider using DesktopServer instead (along with Coda 2). Unlike MAMP, you can work on template theme files directly with WYSIWYG preview, LAN share for mobile device testing (with WordPress, -not just HTML sites), enables AirPreview to work with WordPress, copy, import/export to live sites, etc. Setup is easy as it manages your vhosts, database, and project files in about three mouse clicks:
http://www.youtube.com/watch?v=Pw9-F8etBPY
Related
I'm using MAMP Pro v3.5 for local development. I have multiple dev sites running successfully without a problem. When it came to testing a site on my phone, I used the out of the both 'Name resolution [x] via Xip.io (LAN only)' option under the hosts tab. The first host I turned that on with was fine and worked very well (using address like www.siteone.dev.192.168.0.10.xip.io).
The problem came though when I attempted to setup a second dev site on Xip.io using the above method. Now using a different URL (using address like www.sitetwo.dev.192.168.0.10.xip.io) for the second dev site, no matter what I try, I get the first host that was setup rather than the expected second.
Is this a bug with MAMP Pro, or it's just not capable. I've tried turning off the 1st host I setup with MAMP Pro, but it still shows up as the site that is getting served under the second xip.io address I setup.
Would really appreciate one of the MAMP people to respond and confirm if this is expected behaviour. An extended Google search didn't turn up anything.
Thanks
Brendan
I have two Macs (Macbook Air & iMac) and want to use Dropbox as the source for local website files and their corresponding databases.
I setup the databases following these instructions (text version here), moved the website files to Dropbox and synced the contents on both devices.
I've ensured that the correct files are in place as per virtual host instructions for MAMP, such as:
added the domains to my hosts file at /etc/hosts
uncommented the httpd.conf to include httpd-vhosts.conf
added the ServerName and DocumentRoot like I'm supposed to (even changing out my user name in the path)
My laptop (the original computer where the sites were developed) works fine with the migrated databases and site files, but but when I start up MAMP and go to any dev virtual host url on my iMac, I'm met with a MAMP favicon and a blank screen with no content whatsoever.
How can I get my desktop to play nicely and access the databases correctly without error?
Thanks for any help addressing this issue.
After manually deleting the MAMP folder from the Applications folder, I reinstalled a fresh copy of MAMP and ensured that enough time had passed for my Dropbox to sync, in addition to removing any conflicting file issues.
It seems that giving yourself a significant time delay between firing up MAMP on either machine helps in preventing database conflicts that must've been causing the issue.
I normally develop in ruby and serve my developement site with pow.cx.
For some client work I have to work with php and drupal. I had quite a bit of set up problems and incompatibilities between apache / php / Mamp and my pow server.
I've tried to set things up as mentioned there:
https://github.com/37signals/pow/wiki/Running-Pow-with-Apache
When I leave Mamp on port 888 everything is fine, but when i want to run mamp and pow on port 80 i start to have regular problems.
To try to fix the issue I have installed Apple Server app.
I now regret it.
If i turn websites on in the server app. Server takes over my pow url.
If i turn websites off, i can't access the pow url at all (says i have to turn websites on).
If i remove the Server app completely and restart, i can access Pow again, but Mamp refuse to start apache, saying that it can't resolve the domain name set up by the Server App.
So Is there a way to remove and clean the Server app setup completely?
I'm not sure what the cleanest way to remove the Apple Server app. But at least I manage to get Mamp work again.
I had ot add an alias in my /etc/hosts files with the current name of my local machine
127.0.0.1 my-lovely-mac
and now Mamp Apache is all happy again
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.
I'm currently developing a Facebook App for an Application Tab with another developer (CodeIgniter Framework).
It's not possible to use localhost for Application Tabs. So we're using subversion for updating our stuff on our server to test the app in facebook. Quite often we have conflicts in our files, because we're editing the same parts of it.
Is there any better solution to develop a Facebook App with multiple developers?
You could modify your "hosts" file in C:\WINDOWS\system32\drivers\etc
//Under...
127.0.0.1 localhost
//Add...
127.0.0.1 yourappname.com
This will allow you to run the application locally...
Xander is right and here's what we are doing in our dev team :
setup facebook app
setup on our localhost
create a virtual host like dev.facebookapp.com via apache
make sure you have svn or git to lessen conflicts with other dev