dsims (dsims) migrated their old, custom-built trail journal/blog from a self-hosted server to a self-hosted Discourse server, aiming to revitalize the site and experiment with a multi-site setup. The original site aggregated social media posts from a 2010 thru-hike of the Appalachian Trail, and the migration involved recovering hotlinked media, importing comments as inactive users, and redirecting info pages via permalinks. dsims successfully reproduced key features like a chronological topic list, tags for post types, and a map view using the Isabelle theme, Locations plugin, Created Topic Sort theme component, Topic List Thumbnails theme component, and custom CSS. The site is now available at onahike.com. cocococosti praised the site’s appearance and the impressive migration of content from multiple social media platforms, and especially the map. jimkleiber (jimkleiber) was fascinated by the approach, drawing parallels to indieweb.org/PESOS, and inquired about the import strategy for future hikes. dsims (dsims) suggested potential strategies like using the RSS Polling plugin, building a standalone service, or utilizing IFTTT with email-to-Discourse functionality.
Way back in 2010 I built my own blog-like site to aggregate all the social media posts I was making while I thru-hiked the Appalachian Trail. The idea was that I could post, check-in, geo-tag, and upload to various services and collect it all in one spot that people could easily subscribe to and follow my progress and leave comments.
It’s now basically just a static snapshot of that time but it was showing its age and the server is woefully behind on updates. So I decided to migrate it to my self-hosted Discourse server to see how a multi-site setup works.
All the media files in the past were simply hotlinked, so thankfully I was able to recover most of it even if I still lost a few things to bit-rot. Now it’s all safely stored on my server (minus videos). Comments were migrated over as inactive users. The few info-pages I had now redirect to topics via Permalinks. I was able to reproduce all the features I had like a chronological topic list, tags for post-types, categories for States, and a map view.
With this setup I could easily post a future hike (PCT?), or maybe even make it a platform for others to share their own hikes. Check it out at onahike.com.
I haven’t used it yet, but I saw there is a RSS Polling plugin. So my first strategy would be to use that or a modified version that also makes API calls in addition to the RSS feeds.
Or build a standalone service that lives outside Discourse that fetches posts and republishes them via the Discourse API. Or maybe a third-party service like IFTTT could fetch posts and republish them to discourse via email without needing any other glue.