planetperl VS planetdavorg

planetperl has the code that drives Planet Perl (ok, actually, it contains the configuration for that site – most of the actual work is done by Perlanet – and see below for more about that)

title: Planet Perl description: There's More Than One Way To Aggregate It url: https://perl.theplanetarium.org/ author: name: Dave Cross email: [email protected] twitter: davorg entries: 75 entries_per_feed: 5 opml_file: docs/opml.xml page: file: docs/index.html template: index.tt feed: file: docs/atom.xml format: Atom google_ga: G-HD966GMRYP cutoff_duration: months: 1 feeds: - feed: https://www.perl.com/article/index.xml title: perl.com web: https://perl.com/ - feed: https://news.perlfoundation.org/atom.xml title: Perl Foundation News web: https://news.perlfoundation.org/

Previously, my workflows for these sites just needed a single job (called build) but now I added a deploy job which depended on build. For example, the workflow that builds Planet Perl now looks like this:

A little bit more hacking on Planet Perl. You can now filter the sources that you want to see (and those choices are remembered for the next time you visit the site). Thanks to Gabor for suggesting it.

If you'd like to suggest new feeds to add, then raise an issue or submit a pull request on the GitHub repo.

The other file you need is the template for the HTML page. This is usually called “index.tt”. The one I use for Planet Perl is rather complicated (there are all sorts of Javascript tricks in it). The one I use for Planet Davorg is far simpler – and should work well with the config file above. I suggest going with that initially and editing it once you’ve got everything else working.

It was then just a case of changing my GitHub Actions to use my container. Here’s an example of one of the commits that did that.