On Sun, May 28, 2017 at 5:48 PM, sebb <[email protected]> wrote: > I notice that there is now a /srcv/cache directory set up on Whimsy. > > I was wondering what this is intended for? > If it is to be used by multiple scripts, there needs to be some way to > ensure they don't affect each other's files. > > Note: I used /tmp/ for the two HTTP caches. > AFAIK this means stale entries will eventually be dropped by the OS. > I think the whole /tmp tree is likely cleared on reboot. > > In the case of /srv/cache, does there need to be a purging strategy? > Or perhaps the files are 'permanent'
Quick links: https://github.com/apache/whimsy/blob/master/lib/whimsy/asf/podlings.rb#L102 https://github.com/apache/whimsy/blob/master/www/roster/views/actions/ppmc.json.rb#L83 Longer description: On the original whimsy-vm, the svn directories were read/write. That was a train-wreck. Starting with whimsy-vm2, the svn directories are read-only (as in, not writable by the www-data user id that apache httpd uses). These directories will be updated via a cronjob, but not seeing your changes live can be annoying. The board agenda tool has a dedicated /srv/agenda directory for temporary results (uncommitted changes and the like). Updated board_agenda_*.txt files may be placed there, and will be used if the mtime is later than the copy in the svn tree. I just added code to the roster tool to update podlings.xml, and found I had a similar need. Similar code may be useful for committee-info.txt. In each of these cases, there isn't a compelling need to clean up. The files in question aren't that big, and updates overwrite prior versions. - Sam Ruby
