[Expo-tech] databaseReset.py
Sam Wenham
sam at wenhams.co.uk
Tue Feb 18 14:11:45 GMT 2020
I don't have access to the slac so don't see what is going on there. I
haven't run databaseReset.py for ages.
You don't need parser entries any more provided you call the logbook
logbook.html and use the current format, these are set as the defaults
in settings.py a few lines above this table of mess.
Sam
On 18/02/2020 11:15, Philip Sargent (Gmail) wrote:
> See the Slack thread on this.
>
> Who ran an update databaseReset.py in the past couple of days?
>
> https://app.slack.com/client/TQF95LK8T/CSCD0HW3S
>
>
>
> *From:*Philip Sargent (Gmail) [mailto:philip.sargent at gmail.com]
> *Sent:* 17 February 2020 01:48
> *To:* 'expo-tech at lists.wookware.org'
> *Subject:* creating a new year in the expo system
>
>
>
> I am puzzled.
>
> I see that the troggle code had no entry for parsing the 2019 logbook,
>
> so (pulling first) I edited it and git/pushed it to the server.
>
>
>
> But the 2019 year logbook entries had already been parsed and can be seen
>
> http://expo.survex.com/expedition/2019
>
>
>
> so why is troggle code on the server out of date with respect to the
> files produced by troggle?
>
> is there some git equivalent of “hg update” that hasn’t been run ?
>
>
>
> Philip
>
>
> _______________________________________________
> Expo-tech mailing list
> Expo-tech at lists.wookware.org
> https://lists.wookware.org/cgi-bin/mailman/listinfo/expo-tech
>
More information about the Expo-tech
mailing list