From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Denis Maier <maier.de@gmail.com>
Subject: Re: ConTeXt as a service
Date: Wed, 20 Nov 2019 17:43:15 +0100 [thread overview]
Message-ID: <855e8771-67ab-e263-3eb5-81fb704b1d8f@xs4all.nl> (raw)
In-Reply-To: <CAMXdeGHMw3vpBSJtr1MWV+JR9AXetKTkrKxQ8as93YFcNvVpAQ@mail.gmail.com>
On 11/20/2019 5:07 PM, Denis Maier wrote:
> Hi everyone,
> Is it possible to run ConTeXt as a service on a server? If yes, is there
> documentation about this?
> Background: I'm currently on the PKP conference, and we are discussing
> OJS plugins for automated PDF production. I was wondering if ConTeXt
> could be an option...
> Best,
> Denis
>
> P.S.: I'll be giving here a brief introduction to XML typesetting with
> ConTeXt to spread the word... just to let you know.
Running tex on demand is not really a problem but when it has to happen
after clicking a button there is the problem of preventing a (web)
server locking due to such aprocess as a tex run normally takes some
time ... can be a second for some simple document but mayb eminutes for
a 500 page document with images on each page and some 4 runs needed to
get all cross references and lists right
so, one ends up with some independent service with a cue and a way to
query the state of a run
there is actually code in the distribution (or can be added) that can be
used but i never came to document it in detail (it makes no sense if
only i use it) .. it boils down to delegating to one or more vm running
a service that runs and reports status
among the aspects to take into account are:
- are resources needed (can be some mount)
- how long does the result needs to be kept
- when is stuff cleaned up
- how to keep things secure (no problem with xml)
etc
anyway, we have some of such workflows and once they work they do so
forever
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-20 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 16:07 Denis Maier
2019-11-20 16:43 ` Hans Hagen [this message]
2019-11-20 17:10 ` Henning Hraban Ramm
2019-11-20 18:50 ` Hans Hagen
2019-11-22 7:43 ` Jan U. Hasecke
2019-11-22 8:46 ` Mojca Miklavec
2019-11-22 9:05 ` Henning Hraban Ramm
2019-11-22 15:45 ` Jan U. Hasecke
2019-11-22 23:44 ` denis.maier.lists
2019-11-23 7:12 ` Mojca Miklavec
2019-11-23 12:02 ` Henning Hraban Ramm
2019-11-23 12:18 ` luigi scarso
2019-11-23 13:18 ` Henning Hraban Ramm
2019-11-23 14:03 ` mf
2019-11-24 11:00 ` Hans Hagen
2019-11-23 14:14 ` Mojca Miklavec
2019-11-23 15:39 ` Henning Hraban Ramm
2019-11-23 15:50 ` Mojca Miklavec
2019-11-23 16:03 ` Henning Hraban Ramm
2019-11-24 10:56 ` Hans Hagen
2019-11-23 14:24 ` mf
2019-11-23 15:39 ` mf
2019-11-24 10:51 ` Hans Hagen
2019-11-21 2:00 Brian Ballsun-Stanton
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=855e8771-67ab-e263-3eb5-81fb704b1d8f@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=maier.de@gmail.com \
--cc=ntg-context@ntg.nl \
/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).