Step 1/4 to bring back to life my blog on #gemini : ✅
Still work to do but starting is always the hardest (or maybe it won't be, we'll see).
Step 2 will be the most difficult, step 3 and 4 should go quickly and smoothly.

ETA for bringing my blog back on gemini for real: no idea! :D
#geminiprotocole

Step 2/4 to bring back to life my blog on #gemini : ✅
Step 3/4 to bring back to life my blog on #gemini : In (good) progress

This is going faster than expected :-).
Wouldn't be the case if I didn't find lowdown <3

Bringing my blog back to life on #gemini :

  • Step 1/4: Export orgmode to markdown with yaml frontmatter (instead of toml) ✅
  • Step 2/4: Convert markdown to gemtext, including internal links and images (thanks lowdown) ✅
  • Step 3/4: Automate build of the capsule in my CI/CD pipeline (like I did for my website): ✅
  • Step 4/4: Auto deploy after successful build based on ntfy message (like for my blog): In progress!

There is actually a step 5, which is changing DNS to point to the new server, but that is not worth a line in here :-).

I'm actually very happy that my capsule is now generated with a working blog area with working internal links and images, which weren't the case before! For now, all is deployed in an inaccessible capsule as DNS points to the old one, but looking at the success I had in the past days, I think my blog will be back and up to date on gemini by the end of week!
Never thought that would be that quick, just needed the right level of motivation (and finding lowdown was key too).

Bringing my blog back to life on #gemini :

  • 1/5: Fix export from orgmode: ✅
  • 2/5: Convert markdown to gemtext: ✅
  • 3/5: Automate capsule build: ✅
  • 4/5: Auto deploy after successful build: ✅
  • 5/5: Change DNS to new server: waiting for migrating all other capsules first (to change DNS only once - as all capsules have a CNAME entry pointing to my main capsule)

Migrating other capsules to new server:

  • Planet Gemini FR (french capsule aggregator): ✅ (new domain: gemini://planet-gemini.fr)
  • gemini://houston.gmi.bacardi55.io: ✅ (DNS still pointing to old server)
  • gemini://discogem.gmi.bacardi55.io: In progress
  • gemini://tinylog.gmi.bacardi55.io: In progress

Seems that even with new steps and migrations in the list, I'm getting there for real :-).

Well, all steps are done to bring back my blog to #gemini .
All other services (houston, discogem, tinylog aggregator) are migrated as well.
DNS TTL has been reduced to 5min

All I need now is:

  • wait for DNS TTL to be propagated
  • write a gemlog entry and/or a blog post to communicate the updates and changes
  • Change the DNS

I may be AFK for the week end so if it doesn't happen tomorrow, it might wait early next week. But at least all technical steps are done except final dns change :-).

Quite happy about finally being able to pull the trigger very soon :)

I believe the migration is now completed! I changed the DNS configuration so now everything should be pointed to the "new" server…
If you can see this new gemlog post, your DNS is up to date and your browsing the updated capsule:
gemini://gmi.bacardi55.io/gemlog/2025/04/04/capsules-update-april-2025/

Paint is still fresh so i'm sure there are a lot of small issues everywhere, but that's fine, just let me know^^.

#gemini #geminiprotocol

@bacardi55 welcome back :)
@bacardi55 about BBS - you should contact @jk to remove old one or do something with it