Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's what I did:</p> <p><strong>Setup:</strong></p> <ul> <li><p>I'm developing the site on my local computer</p></li> <li><p>Mamp Pro is running on my local computer</p></li> <li><p>I would like other people on the local network to login to the CMS on my computer and update the CMS</p></li> </ul> <p><strong>Server settings:</strong></p> <ul> <li><p>Use the default ports <code>80/3306</code> (just don't have web sharing turned on in OSX prefs) - I'm sure you could use the MAMP ports if you want</p></li> <li><p>Run <code>Apache/MySQL</code> server as users <code>www/mysql</code></p></li> </ul> <p><strong>Virtual host settings:</strong></p> <ul> <li><p>Give your server a name</p></li> <li><p>Leave local name resolution on</p></li> <li><p>Add the IP address of the computer Mamp Pro is running on e.g. <code>192.167.1.1</code></p></li> <li><p>Add a port number (this will be the unique way of identifying sites on the LAN - see below for more) I just used port <code>8888</code> </p></li> <li><p>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"</p></li> <li><p>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</p></li> <li><p>Start the virtual host</p></li> </ul> <p><strong>Accessing the site from another machine on the same LAN:</strong></p> <ul> <li><p>Enter the IP address of the Mamp Pro machine followed by the port number you entered</p></li> <li><p>e.g. <code>http://192.168.1.1:8888/</code></p></li> <li><p>If you have multiple sites, just enter a different port number in the setup</p></li> </ul> <p>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.</p> <p>Please sing out if there's abetter way - this is just how I got it working.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload