I believe that public in this case refers to public assets such as CSS, js, etc., where one puts custom files rather than publicly accessible, e.g., wp-uploads for WordPress.  In the case of most frameworks, URL access is limited to specified routes only which point to controller methods.  ConTeXt, when installed in this manner,  can only be run as www-data:www-data, i.e., by httpd.

I wasn’t able to get it work using any of the other suggestions.  Is there another template you can suggest?

Pavneet Arora
m: +1 (647) 406-6843
e: pavneet_arora@waroc.com

From: Henning Hraban Ramm
Sent: Saturday, July 9, 2016 16:56
To: pavneet_arora@waroc.com; mailing list for ConTeXt users
Subject: Re: [NTG-context] Invoking ConTeXt from inside php web appliction

…

I’m quite sure it’s a bad idea to install ConTeXt (or anything like that) in a public, i.e. web-accessible, directory!

Even if I can’t imagine an attack via accessing files from the ConTeXt tree, experienced attackers might.

I don’t use PHP any more, but I’m quite sure there’s a better way.