From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt as a service
Date: Fri, 22 Nov 2019 08:43:09 +0100 [thread overview]
Message-ID: <69b9a60b-20f9-4aa0-d7a0-85b4bb6226d5@mailbox.org> (raw)
In-Reply-To: <C3157962-00EF-4C43-8244-045D805FF5E4@fiee.net>
Am 20.11.19 um 18:10 schrieb Henning Hraban Ramm:
> Hi!
>
> I’m running ConTeXt on my web server e.g. to generate shipping forms for a customer.
>
> As Hans said, it makes sense to use an asynchronous setup; in my case it’s celery/RabbitMQ behind Django.
>
> You probably need to set a few environment variables: I find HOME, PATH, TEXROOT and TEXMFOS in my setup. I don’t know if you really need all of them, it’s already running for several years…
> Also your web server process might only run binaries that belong to some user/group like wwwrun.
>
> It won’t work in shared hosting, because you can’t install your own programs.
Generally this is correct. But there are providers such as the
Hostsharing cooperative where it is possible to install programs in a
shared hosting environment. We do it for years. ;-)
> Otherwise: What kind of documentation do you need? Installing ConTeXt on a (web) server is not different from any other Linux system. Calling ConTeXt from a web application is not different from calling any other external program. The rest depends on your setup and web frameworks.
I am very interested in running ConTeXt as a service, too. I am still
nurturing the idea of a publishing cooperative for self publishers with
a Markdown --> Pandoc --> ConTeXt workflow with a nice web frontend. I
hope to make it to the next ConTeXt meeting to discuss it.
Many greetings
juh
--
Hostsharing eG – die Hosting-Genossenschaft
Souveränität – Nachhaltigkeit – Exzellenz
https://www.hostsharing.net
___________________________________________________________________________________
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-22 7: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
2019-11-20 17:10 ` Henning Hraban Ramm
2019-11-20 18:50 ` Hans Hagen
2019-11-22 7:43 ` Jan U. Hasecke [this message]
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=69b9a60b-20f9-4aa0-d7a0-85b4bb6226d5@mailbox.org \
--to=juh+ntg-context@mailbox.org \
--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).