My fork of nyptu's gemlog.sh
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
FIGBERT d07176738c
Fix date timezone substitution
9 months ago
sample-configs change toot formatting and smaple footer 9 months ago
LICENSE initial commit 1 year ago
README.md Update README.md 9 months ago
config.sh changed installation instructions 1 year ago
footer.gmi changed installation instructions 1 year ago
gemlog.sh Fix date timezone substitution 9 months ago
header.gmi changed installation instructions 1 year ago

README.md

gemlog.sh

FIGBERT's fork of nytpu's gemlog.sh, a utility for writing and managing gemini logs (gemlogs) and atom feeds without needing a cgi script.

dependencies

  • sh and all its goodies (duh)
  • perl
  • date
  • tr
  • sed

install

  1. git clone https://git.figbert.com/FIGBERT/gemlog.sh
  2. cd gemlog.sh
  3. symlink gemlog.sh to anywhere in your $PATH
  4. mkdir ~/.config/gemlog.sh
  5. cp config.sh header.gmi footer.gmi ~/.config/gemlog.sh/
  6. modify ~/.config/gemlog.sh/config.sh with all of your config settings, ~/.config/gemlog.sh/header.gmi with what you want your header to be, and ~/.config/gemlog.sh/footer.gmi with what you want your footer to be

Expansion of variables from config.sh is supported in both the header and footer.

usage

  1. Write your post in .gmi format. The first header of any level on the page will be used as a title (it doesn't have to be on the first line). The script will detect any .gmi files that start with a number and assume they're blog posts. Name your files like YYYY-MM-DD.gmi or YYYY-MM-DD-[title-here].gmi so you get them sorted nicely in reverse chronological order.
  2. make sure you're in your gemlog directory then run gemlog.sh to build the index page and the atom feed
  3. if you want your atom feed to be accessible over the web as well as gemini, symlink the atom.xml file to your web server directory

contributing

To contribute to upstream, send patches, suggestions, and bug reports to ~nytpu/public-inbox@lists.sr.ht. Otherwise just open an issue on this repo.