Hi Kevin, You are correct on the following: I think the reason maybe appserver and www-data are the same group in www-data. is that right?-- Correct. That is because you created an "appserver" user and added the user to the "www-data" group and the assets you have at least have "read" ability for the "www-data" group. This would solve the permissions issue with httpd/Apache2 being able to access your assets. I created new user appserver and add it to www-data group. I am running wotaskd and Monitor as appserver.-- Also your question here: What is "WebObjectsDocumentRoot" for in webobjects.conf? because we use 'Alias /WebObjects" in apache2.conf? do we need "WebObjectsDocumentRoot"?-- The "WebObjectsDocumentRoot" is used by the WO Apache HTTP Adaptor to know where your WO application lives on the system. Normally in Apache, you'd set the CGI_DOCUMENT_ROOT, but this directive handles it for you, at least according to the documentation I've read over. Both the "WebObjectsDocumentRoot" and applicable "Alias" directives are required for WO 5.4 to operate correctly with Apache2. Cheers, Daniel -- Daniel Kao - Seattle, WA, U.S.A. Übermind, Inc. * http://ubermind.com/ * "Your Vision, Our Experience" WOlastic * http://wolastic.com/ * "WebObjects in the Cloud" Ren, Xiaowen wrote:
|
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com