In the Navicat Lite download it included a folder with connection scripts for setting up HTTP Tunnel. I see in the connection files in Dreamweaver that in the MAC folder it says that it is going to use HTTP as the connection method if it detects that it is on a Mac computer. either localhost or localhost.8888 works, depending on whether I have started MAMP in 80 & 3306 or 8888 & 8889 for apache & mysql. The Dreamweaver site shows that my local and testing server urls are working. I have all the Dreamweaver site files in the Mamp htdocs folder. I have removed connections and started over. etc.īut every single connection that I create or try to re-use from days ago fails. I have changed PHP and Mysql ports back and forth between 8888 & 8889 to 80 & 3306, I have done terminal sudo commands to create a “symbolic” link between the mysql socket in MAMP in the Application folder etc. I have spent two days going from “solution” to solution. Navicat Lite which I just installed today sees my mysql databases perfectly and immediately.ĭreamweaver CS4 fails in every possible way to see the tables. Mamp’s PHP Admin sees databases just fine. I reinstalled MAMP after saving the db folder and reinstalling it. No more repeated crashes.īut I could not get the Dreamweaver connections actions to see databases any more. I had to get rid of a Configuration-1 that had formed. My Dreamweaver CS4 was also starting to crash. Please sing out if there's abetter way - this is just how I got it working.2 days ago on my MacPro OS 10.6.8 I uploaded the latest Adobe updates. This works for me and staff can now edit the CMS and view the site but it seems a bit 'hacky' to me using a different port for each site as the way to differentiate sites in development. If you have multiple sites, just enter a different port number in the setup If the above step doesn't work properly, you'll now need to CMD + I the website directory and ensure your local machine admin has rights to read and write to the directory - be sure to click the cog and select "Apply to enclosed items" so the rights get applied to the directories insideĪccessing the site from another machine on the same LAN:Įnter the IP address of the Mamp Pro machine followed by the port number you entered If you had a site setup prior to switching the Apache/MySQL users, click the "Permissions" button under the disk location and set owner to www and the group to admin so your local admin account has access - click "Set" Run Apache/MySQL server as users 192.167.1.1Īdd a port number (this will be the unique way of identifying sites on the LAN - see below for more) I just used port 8888 Use the default ports 80/3306 (just don't have web sharing turned on in OSX prefs) - I'm sure you could use the MAMP ports if you want I would like other people on the local network to login to the CMS on my computer and update the CMS I'm developing the site on my local computer Sorry if this is easy but for a paid product, Mamp Pro help and support is pretty scarce and I suspect this stuff is easy if you know how to setup a linux server - but if you don't know how to do this, it's why you purchase MAMP Pro right? Running Apache/Mysql as Ports: What is more secure, running Mamp Pro using ports 8888/8889 or the defaults of 80/3306? And is the only difference adding/not adding port numbers when viewing sites?Īccess to sites by users on the same LAN: What are the steps for getting this working - the firewall on the MAMP Pro machine is currently off to test the basic setup but no one on our local network can connect to the sites - have tried 192.168.0.1:8888 & virtualhostname:8888 I've been researching how to setup a LAN Mamp Pro server so local users can edit/view sites - but there seems to be a lot of confusion (at least I'm confused based on why I've read).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |