Now in your vhosts, you will set your NameVirtualHosts config, and your default virtual host, followed by your other vhosts: This is usually set to 127.0.0.1 or localhost, and typically followed by a Directory directive block with some permissions settings Then in your nf change your ServerName directive to match the new hostname. In your hosts file, give your machine a name other than localhost on the first line where it sets 127.0.0.1 to localhost: In order to accomplish this, I recommend changing 3 files: etc/hosts, nf and nf. Apache will attempt to match the provided host against all of your named vhosts, and when it fails, it will serve your default vhost (which is your first listed vhost) by default. first a NameVirtualHost directive, then a master vhost (your localhost), followed by your regular vhosts. Your Vhosts config needs a few things before you start listing Vhosts in order for localhost to work. To accomplish this, you need to set up your apache config to allow vhosts, (i'm assuming you've already taken care of that). it has to be configured so it's the default vhost. This will need to added to the vhosts, but it can't be added just like any other. Please sing out if there's abetter way - this is just how I got it working.Yes, this is possible. 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
#MAMP PRO TOTAL MAX VIRUTAL HOSTS UPDATE#
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
#MAMP PRO TOTAL MAX VIRUTAL HOSTS HOW TO#
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 kommentar(er)
