I forgot to add: Rens Oliemans <[email protected]> writes: > It has the benefit of not > having to modify worg source, but doesn't overcome the same limitation > (publish.sh only looks at modified files).
This also means that automatically looking up currently working instances on the fly won't actually help update (all) the links on the fly. Not unless the code detects a change of instance and triggers re-publishing. I haven't looked at the libredirect json; will have a flag set when an instance has changed? Otherwise we'd need to save state and compare the current list with the last one retrieved. (If the automated approach gets complicated -- also see: error handling -- we could take a semi-automatic or manual approach with the maintainer in the loop; Rens' code for the lookup would help for that too.) cm
