Since ACLs are not in use in the standard OS install there is no ability for the permissions to be carried into child folders and their contents. In order to do this we give access to our authorized groups. Our web site is updated regularly with photos manually deposited into folders in the web site root. The problem with installing on a 10.9 non-server is that you do not have the ability, as far as I know, to use ACLs to control access to the folders containing the web site.
Due to that issue, we have purchased a new Mac Mini Server but did not install that Server software to put the WPE and custom web publishing web site on. I am not enamored of FileMaker's choice to usurp full control of Apache but I am trying to move forward rather than rant. So we contacted FileMaker and following their recommendation that the WPE NOT be run on a 10.9 server, we installed it on a standard install of the 10.9 OS which is bound to our 10.9 Open Directory. I did that twice before I realized that the issue would not go away. There appears to be no way to reinstate the FileMaker precedence without reinstalling. On restart of the machine though, the Mac OS Server takes it back and, even though the websites section of the Mac 10.9 Server software is not on, presents the message that the websites are not on and to contact the admin for the server to enable them. On install FileMaker Server takes full control of Apache and runs FMS as expected. First discovery was of the issue that putting a FileMaker server on a 10.9 Server does not work after the first restart. We recently moved to FileMaker Server 13 on and discovered the following issues during production use on Mac 10.9.
0 kommentar(er)
