Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • E etherdump
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • decentral1se
  • etherdump
  • Issues
  • #1

Closed
Open
Created Nov 04, 2019 by colm@colmMaintainer

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 !

C

Assignee
Assign to
Time tracking