From: Henning Hraban Ramm <texml@fiee.net>
To: pavneet_arora@waroc.com,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Invoking ConTeXt from inside php web appliction
Date: Sat, 9 Jul 2016 22:56:24 +0200 [thread overview]
Message-ID: <A67D27D2-D61C-4C40-8740-CC1ED58D850B@fiee.net> (raw)
In-Reply-To: <eb37bc1153d454e2f1e645068e8262bf.squirrel@webmail.pavastupa.com>
Am 2016-07-09 um 17:45 schrieb Pavneet Arora <pavneet_arora@waroc.com>:
> Sorry that this has taken me so long. The report card application has
> been deployed, and although I am still going through and resolving minor
> bugs, it is very much in use (350 students leaving on Tu who already have
> their foundation work marked and commented within the system; output via
> ConTeXt).
Nice to hear about your success!
In my case, my customer, a publisher of several special interest magazines, uploads lists of customers and their ad bookings into my web app and gets nicely TeXed voucher shipping documents.
> Anyway, I have updated the Wiki, but am unsure if I missed anything. So
> can everyone have a look and let me know:
> http://wiki.contextgarden.net/ConTeXt_Standalone#Apache_webserver_installation
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.
I run ConTeXt from a Django (Python) web app behind Nginx, and there only static files (i.e. images, CSS etc.) are directly accessible, and I can call a system-wide installed ConTeXt owned by root (i.e. nobody else can change it).
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-09 20:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 15:45 Pavneet Arora
2016-07-09 20:56 ` Henning Hraban Ramm [this message]
2016-07-09 23:02 ` Pavneet Arora
[not found] ` <CAG5iGsD48qgiHcSjXYERcXrP4fo6pYL0SJTkz7JVqS9bLM+8bA@mail.gmail.com>
2016-07-11 16:14 ` Pavneet Arora
-- strict thread matches above, loose matches on Subject: below --
2016-06-17 12:16 Pavneet Arora
2016-06-17 12:21 ` luigi scarso
2016-06-17 12:25 ` Pavneet Arora
2016-06-17 12:34 ` luigi scarso
2016-07-11 12:50 ` massifr
2016-06-17 12:42 ` Pavneet Arora
2016-06-17 13:25 ` luigi scarso
2016-06-17 13:39 ` Pavneet Arora
2016-06-17 14:15 ` Hans Hagen
[not found] ` <CAG5iGsBpLw8uTFyH7E5MCqcEoaK82qbyakfJA3teeUkSinQEgg@mail.gmail.com>
2016-06-17 14:57 ` Pavneet Arora
2016-06-17 18:49 ` Henning Hraban Ramm
2016-06-17 20:06 ` Mojca Miklavec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A67D27D2-D61C-4C40-8740-CC1ED58D850B@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
--cc=pavneet_arora@waroc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).