ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: Pavneet Arora <pavneet_arora@waroc.com>,
	 mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Invoking ConTeXt from inside php web appliction
Date: Fri, 17 Jun 2016 14:21:44 +0200	[thread overview]
Message-ID: <CAG5iGsBAZ4rwf_dtnZXe1MX56TJxuaUjkF-cesu8Nx+aKMw4EA@mail.gmail.com> (raw)
In-Reply-To: <20160617121655.GC34324@lahore>


[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]

On Fri, Jun 17, 2016 at 2:16 PM, Pavneet Arora <pavneet_arora@waroc.com>
wrote:

> I am stuggling with getting ConTeXt to run from inside a php script
> under Apache.  First off, let me say that the installation works fine
> from the command line as a logged in user.
>
> Initially, I tried to do it inline:
>
>   cmd = ". /opt/context/tex/setuptex /opt/context/tex/setuptex; cd
> $spool_dir; context $full_input_filename";
>   system($cmd);
>
> which returns exit status 2, "Incorrect usage".
>
> Then I created a small bash script with the following lines:
>
>   #!/usr/bin/env bash
>
>   . /opt/context/tex/setuptex /opt/context/tex
>   context $1
>
> When I trap the output, I get the following error in the log file:
>
>   resolvers       | caches | fatal error: there is no valid writable cache
> path defined
>
> I also attempted this manually at a bash prompt resulting in the same
> error:
>
>   sudo -u www-data bash -c bin/proccontext.sh $FILENAME
>
> What would be the correct design pattern to invoke ConTeXt from a web
> application?  This is all under Ubuntu 14.04, BTW.
>
> advTHANKSance
>
>
permissions ?

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 1740 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-06-17 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17 12:16 Pavneet Arora
2016-06-17 12:21 ` luigi scarso [this message]
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
2016-07-09 15:45 Pavneet Arora
2016-07-09 20:56 ` Henning Hraban Ramm
2016-07-09 23:02   ` Pavneet Arora
     [not found]     ` <CAG5iGsD48qgiHcSjXYERcXrP4fo6pYL0SJTkz7JVqS9bLM+8bA@mail.gmail.com>
2016-07-11 16:14       ` Pavneet Arora

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=CAG5iGsBAZ4rwf_dtnZXe1MX56TJxuaUjkF-cesu8Nx+aKMw4EA@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --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).