💾 Archived View for bbs.geminispace.org › s › Geminispace › 6553 captured on 2024-05-10 at 11:23:37. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-03-21)
-=-=-=-=-=-=-
My capsule mess
I have a two years old capsule, more or less, anything the thing is that I started adding posts "just to try Gemini" so with no concerns for any file structure. Now it seems that I'm settled with chronological folder structure where my gemlog posts are in year/month/ But what do I do with my old posts? My guess is that I should move them to integrate them in the new structure, and add redirections to reflect their new locations... but that's something I've never done "by hand", and I'm not sure I'm interprenting Agate's documentation right. Should it be something like:
31 old/path/file.gmi new/path/file.gmi?
2023-10-26 · 6 months ago
🕹️ skyjake [...] · 2023-10-26 at 15:28:
Setting up redirects is the recommended way to handle reorganizations, yes.
In the Agate .meta files, the format is:
old/path.gmi: 31 new/path.gmi
The part before the colon can be a wildcard, in which case every matching "old path" will redirect to the same destination.
🍵 michaelnordmeyer [mod] · 2023-10-26 at 15:50:
Skyjake is right, but old path and new path are treated differently in Agate regarding slashes.
If the old URL is gemini://example.com/blog/old.gmi and the new URL is gemini://example.com/gemlog/new.gmi, then the redirection in .meta should be:
blog/old.gmi: 31 /gemlog/new.gmi
The naive but wrong approaches are
blog/old.gmi: 31 gemlog/new.gmi
and
/blog/old.gmi: 31 /gemlog/new.gmi
which would rewrite gemini://example.com/blog/old.gmi to gemini://example.com/blog/gemlog/old.gmi.
🏕️ Yretek [OP] · 2023-10-26 at 20:55:
It seems to be working. It's a bit of a chore, but I'll get it done, thank you :)