Pumping pads as files into publishing frameworks!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Michael Murtaugh 40a4a90535 pull with html5tidy and version links 9 years ago
bin updated help strings of commands 9 years ago
etherdump pull with html5tidy and version links 9 years ago
.gitignore new things 9 years ago
LICENSE.txt added license document 9 years ago
README.md new pull, new meta style from live constant etherdumpÄ 9 years ago
padinfo.sample.json continued tweaks 9 years ago
setup.py subcommands 9 years ago

README.md

etherdump

Tool to publish etherpad pages to files.

Requirements

None beyond standard lib.

Installation

python setup.py install

Padinfo file

All pad-specific settings are loaded from a file called "padinfo.json" -- by default etherdump looks in the current directory. Make a copy of padinfo.sample.json to start one. Make sure to check that the URL and port settings are correct, and to paste the correct apikey here!

cp padinfo.sample.json ~/yourfolder/padinfo.json
nano padinfo.json

And then for instance:

etherdump list

subcommands

  • sync
  • list
  • listauthors
  • gettext
  • gethtml
  • creatediffhtml
  • revisionscount

To get help on a subcommand:

etherdump revisionscount --help

file sync

epfs? pad to file

etherdump init http://localhost:9001/ --path foo etherdump status compare state of files to etherpad & report etherdump pull <padid/path> etherdump sync push / pull file contents to pad

why

Etherdump is useful as a means of dumping the contents of etherpad to files, as a way of opening up the contents of the service to other services / methods / uses / tools / situations. (Files also of course allow for archival tools / methods)