06 January 2009, 20:35

This actually had caused the problem. Now it seems to work fine.

 

Thanks for the great support.

 

Beate 

17 February 2009, 7:43

Enabling "exec" is a serious security risk especially on shared servers. You should really consider making the photo upload different since this won't work on the 90% of the shared servers out there...

17 February 2009, 16:50

Hi...

1. Using "exec" isn't desirable, yes, but the risk can be managed with appropriate use of escapeshellarg and appropriate functions. I challenge you to find an issue in how it's used in Mahara 1.0
2. Mahara 1.1 does away with exec for file uploads, partly because we know it's more portable, but also partly because the file detection using it is no where near perfect.
3. Mahara is not explicitly designed to run on shared hosting. While it can, depending on the host, we won't make design  or implementation compromises just to satisfy shared hosting.

03 June 2009, 14:03

Ok, it took a while due to different priorities i had to set. Some minutes ago i have added a documentation of my current setup of mahara and nginx (0.72) to the wiki. As there are several (evolving) possibilities to start up and control the start and the spawning off of the fastcgi processes, i intentionally do not show my example. It is actually a very basic setup. My documentation actually describes the (nginx-) vhost this mahara installation is running in along with some other stuff.

If someone feels the need to see also the startup scipts for nginx and for fastcgi, please drop me a note.

 

Beate 

03 June 2009, 18:06

Hi - I had a quick read, and added a paragraph about us not officially supporting it - just so people are aware that there might be problems. Still, I don't forsee many issues with it. Thanks for the contribution, I'm sure it will help people who need performance!