💾 Archived View for rawtext.club › ~sloum › geminilist › 007011.gmi captured on 2024-02-05 at 10:53:34. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
ew.gemini ew.gemini at nassur.net
Sun Aug 15 13:13:50 BST 2021
- - - - - - - - - - - - - - - - - - -
Hello,
Andrew Singleton <singletona082 at gmail.com> writes:
What do you guys use?
Interesting collection of answers, thank you all.
Me:
I use emacs to write .gmi files. I use fundamental mode, notgemini-mode.
Then I create the new indices using make and shell scripts. Istart a local (very old!) instance of agate (v1.2.2) to servethe new stuff on localhost, I use emacs/elpher to view the newlycreated content.
Once content I call make again. This will create html files (byshell script as well), recreate indices, checksum and signaturefiles and the atom feed. I check this state into git.
Then I push this state to sourcehut and let the CI create thenew state of gemini/html pages.
I also serve the gemlog from a local machine behind a onionsite. The content ist one "git pull" away.
And I have a clone of the git repo on another small machine inmy house. so another git push.
Once the new content appears on sourcehut, I call "make ping",which calls Antenna to indicate new entries.
The Makefile and all scripts are available here:https://git.sr.ht/~ew/ew.srht.site/tree
tl;dr:emacs, elpher, make, shell, gnupg, signify-openbsd, git,sourcehut-ci, sourcehut.sites.
Cheers,~ew
-- Keep it simple!