Question regarding order of operations in etherdump
Hi etherdump forkers,
Running a little etherbox instance here getting ready for a 2 day retreat with unknown internet situation here;
Etherbox works well enough out of the box, but I'm having issues understanding etherdump itself. I'd have a few questions about what happens in what order, but mostly I'm interested in this:
— why is it that when I delete a specific pad (using the API for example like this http://yourserver.org:9001/api/1/deletePad?apikey=yourkey&padID=mypad) and etherdump is re-run, why does it still appear in the etherdump index ?
I see many component files based off of each pad; guide.html, guide.index, guide.index.diff.html, guide.index.meta.json for example; is it because these files still exist in the etherdump home folder that the index still considers them 'indexable' ?
If so, what should one do, manually delete the pad then these files if a pad gets created by accident ?
thanks a mil !