Limitions on OSX?

[northpoint]

Apologies if this has been covered before; I could not find it.

I would like to move my Alfresco Community system to a server.  We are an engineering firm, so technical but too small to have an IT department.  We also have done everything to date peer to peer, so we have no existing server.  Because of this, and perceived advantages of simplicity, support, and licensing costs, I am considering putting Alfresco on a Mac OSX Lion server, even though most of our workstations are Windows based.  My question is, are there limitations of functionality based on OS in Alfresco Community?  Are there features, extensions, add-ons etc that just do not work in OSX because Alfresco was written natively in a different OS?

I don't want to "gain" the simplicity of Mac server at the cost of crippling Alfresco.

Thoughts appreciated.

[mrogers]

Most of Alfresco is developed on Mac anyway!

MacOS should be fine.

[fiferyan]

We do all of our development on Macs too but we deploy to linux servers.

Here are the only real issues we've found:

• SWFTools is not readily available as a downloadable DMG. You'll probably need to use a package system like macports or compile it yourself. Generating previews of files on the document details page requires this package.


• If you use CIFS, and want to mount the drive locally (on localhost), MacOS won't let you. You need to use the IP address of your local machine. Other machines can mount the drive just fine, it's only the same server that alfresco is running on where you have restrictions. We do this read-only for  file processing with an external service and are hoping to drop this requirement in our installation moving forward because it's not very fast and slightly troublesome on the Mac.

Ryan