search

apache / infrastructure-actions

Apache infrastructure
https://infrastructure.apache.org/
1 stars 3 forks source link

Regression: Presence of *.ezmd files won't be checked after initial conversion of pelicanconf.yaml #4

Closed sebbASF closed 5 months ago

sebbASF commented 5 months ago

The conversion of pelicanconf.yaml to pelicanconf.py depends on an external setting, viz: the presence of any *.ezmd files: https://github.com/apache/infrastructure-actions/blob/475d8f649ab3fa835cb9c79a44938d8d75a75ab3/pelican/migration/generate_settings.py#L158

This means that subsequent changes to the website source won't automatically be reflected in the build settings.

gstein commented 5 months ago

If a projects add .ezmd files, then they should add asfreader to the plugins.

The generate_settings.py script is a one-time migration to move a site, as it exists at that point in time, to the new GHA-based Pelican system. Future changes to the site content may require future tweaks to the config file.

gstein commented 5 months ago

https://github.com/search?q=org%3Aapache+path%3A**%2F*.ezmd&type=code

Shows three repositories with .ezmd files: www-site, template-site, and openwebbeans-site

sebbASF commented 5 months ago

I added a comment to the template, as the connection between *.ezmd and asfreader plugin is not obvious

gstein commented 5 months ago

The connection not obvious, yeah. .. Thank you!