From: tantalum <sph@posteo.eu>
To: guile-user@gnu.org
Subject: Re: Web development
Date: Mon, 07 Sep 2020 09:35:28 +0000 [thread overview]
Message-ID: <cec9f276b4fa7b7cbb9a0c61ed53fde8@posteo.de> (raw)
this is what i use for web development:
* for static files, i use nginx and convert markdown to html using
guile-commonmark, with an extension that allows calls to scheme code
inside markdown (https://github.com/sph-mn/sph-web-publish) to generate
some content like file listings
* for dynamically generated pages, i use nginx and scgi (like fastcgi
but simpler, http://python.ca/scgi/protocol.txt,
https://github.com/sph-mn/sph-lib/blob/master/modules/sph/scgi.scm) to
call a guile procedure on request. the guile side uses this framework
https://github.com/sph-mn/sph-web-app
* for serving generated files, i use the x-accel-redirect (x-sendfile)
response header to instruct nginx to serve the file
* for example, the linked pages here http://sph.mn/other/utilities.html
are generated on the fly with guile 3. guile is fast. some of the
converters use external tools and have a long initial output delay for a
yet unknown reason
next reply other threads:[~2020-09-07 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 9:35 tantalum [this message]
2020-09-07 19:53 ` Web development Zelphir Kaltstahl
-- strict thread matches above, loose matches on Subject: below --
2020-09-04 15:43 Zelphir Kaltstahl
2020-09-04 16:44 ` Ricardo Wurmus
2020-09-04 20:09 ` Zelphir Kaltstahl
2020-09-04 20:25 ` Ricardo Wurmus
2019-10-20 6:10 Diversification [ branched from Re: conflicts in the gnu project now affect guile] Todor Kondić
2019-10-20 6:14 ` John Cowan
2019-10-23 6:16 ` Amirouche Boubekki
2019-10-23 6:48 ` pelzflorian (Florian Pelz)
2019-10-23 10:37 ` Chris Vine
2019-10-23 11:25 ` pelzflorian (Florian Pelz)
2019-10-23 12:33 ` pelzflorian (Florian Pelz)
2019-10-23 19:19 ` Zelphir Kaltstahl
2020-09-05 6:15 ` Joshua Branson via General Guile related discussions
2020-09-05 11:50 ` Web development Zelphir Kaltstahl
2020-09-05 13:09 ` Ricardo Wurmus
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cec9f276b4fa7b7cbb9a0c61ed53fde8@posteo.de \
--to=sph@posteo.eu \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).