sebb wrote on 2020-5-24 6:44AM EDT: > On Sun, 24 May 2020 at 01:00, Sam Ruby <ru...@intertwingly.net> wrote: >> >> On Sat, May 23, 2020 at 6:01 PM Craig Russell <apache....@gmail.com> wrote: ...snip... >> Something to explore as an alternative. Much of what you describe >> could be implemented by a separate tool as a CGI. There are >> advantages and disadvantages to both approaches, ultimately it is up >> to the person doing the coding. >> >> An example of a CGI that lets you fill out a form that is committed to SVN: >> >> https://github.com/apache/whimsy/blob/master/www/members/proxy.cgi >> >> An example of a CGI that updates a YAML file: >> >> https://github.com/apache/whimsy/blob/master/www/members/inactive.cgi >> >> In general, a separate CGI is easier to get up and running quickly. > > It's likely easier to test.
Yeah, an individual CGI for this specific and occasional update is the best bet. Another example shows building a fancier form with input fields using utility functions in whimsy/asf/forms, and allows round-trip read of a JSON, user edits, user submits (which does a svn ci): https://github.com/apache/whimsy/blob/master/www/members/mentor-update.cgi -- - Shane Whimsy PMC The Apache Software Foundation
