💾 Archived View for bbs.geminispace.org › s › Gemini › 17679 captured on 2024-08-25 at 02:10:01. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-08-18)
-=-=-=-=-=-=-
How do you prefer to write your gemlogs?
In the past I've done it straight on my server with nano or vi, and I've also experimented with writing everything locally and then using scp to copy thew new files over. Both seem to be equally good for my purposes as long as I have my column width set appropriately in my editor.
I considered writing things and then uploading with Titan, but my current capsule software doesn't support Titan that I'm aware of and, either way, I was concerned about the slightly larger attack surface.
What do you all use and prefer?
Jun 05 · 3 months ago · 👍 jsreed5, norayr
🕹️ skyjake [mod...] · Jun 05 at 17:53:
I write locally either in a text editor or in Lagrange, and upload via Titan. The script that processes the upload also commits the new or updated content to a Git repository.
either ssh in and use vi, or I use my titan script that I made via Lagrange.
I mounted the Gemini capsule’s folder via SSHFS over Tailscale. So I can access my home server from my phone as well and write using Textastic on iOS which can sync. But I am thinking about writing a TUI admin panel for myself, so I can SSH in and write up things that way.
For tinylogs I created an alias that adds an entry to the SSH-mounted folder. It kinda feels like “tweeting” from the terminal.
I write them with Micro and I manually copy each gemlog with MC... ^^;
I manage my capsule using git. To publish a new log, I copy a template to a new file, write what I want in it, run a script to regenerate my log index pages, commit, and push it up. This allows me to compose logs from any device by simply cloning the repository.
@jsreed5 do you automate the pull?
@gritty I don't automate the pull from the capsule to my devices--and that has bitten me before! Technically I have a bare repository on the capsule server to push and pull from, and Jetforce serves the capsule files from a local clone of the bare repository. That clone does pull automatically.
@jsreed5 I've not done this on the server. githooks?
@gritty That's correct. I don't use Titan so I can't post the hook as a multiline comment here, but I use the "post-update" hook in the bare repo to cd to the local clone, unset the GIT_DIR variable (which otherwise defaults to the bare repo directory), and pull.