From: Brian Ballsun-Stanton <brian@drbbs.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: ConTeXt as a service
Date: Thu, 21 Nov 2019 13:00:35 +1100 [thread overview]
Message-ID: <CADs1X4_iBgJk71o6_vLtZbMOUqxkshVxauUW+oYyfzcVhZTcWw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
In reply to: https://mailman.ntg.nl/pipermail/ntg-context/2019/096313.html
I personally run ConTeXt as a service (as a sort of do-it-yourself
Overleaf).
I use floobits (https://floobits.com/Denubis) as an intermediary code
server, and their floomatic sevice(https://floobits.com/help/floomatic)
running on a server I have. That then calls a shell script that invokes
ConTeXt, which writes logs and pdfs to an nginx monitored folder. It's been
running for about 4 years now and has been solid enough for me to use
without thinking too much about.
Happy to share code and details. My deployment is super-hacky, but it works?
-Brian
[-- Attachment #1.2: Type: text/html, Size: 930 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-11-21 2:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 2:00 Brian Ballsun-Stanton [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=CADs1X4_iBgJk71o6_vLtZbMOUqxkshVxauUW+oYyfzcVhZTcWw@mail.gmail.com \
--to=brian@drbbs.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).