Everyone,<div><br></div><div><br></div><div>As many of you know, the Koha demos currently linked to <a href="http://koha-community.org" target="_blank">koha-community.org</a> are hosted by ByWater Solutions. This morning we noticed some offensive vandalism on the main staff page. It has been removed, but it's gotten us thinking about how we can secure the demos better against such things in the future. </div>
<div><br></div><div>Current thinking is that we should set the database up to refresh from a clean copy every hour. This would limit exposure to offensive damage to a brief window, but would also mean that anyone taking a tour and adding test records may lose them midway through their explorations. A brief note to this effect should be put both outside and inside the demo, but it would still prove annoying.</div>
<div><br></div><div>Rather than acting unilaterally upon a community resource, we thought it would be best to get the community's opinions on how best to handle this. Is an hour too narrow a window? Should we only refresh certain tables (like systempreferences) and leave others (like biblios or borrowers)? Are there other methods we should consider?</div>
<div><br></div><div>My goal is to get this taken care of by the end of the day. If good ideas come in after that, though, I am of course willing to change course.</div><div><br></div><div>Cheers,</div><div><br></div><div>
<br></div><div>-Ian Walls</div><div>Lead Developer</div><div>ByWater Solutions</div>