Pumping pads as files into publishing frameworks!
Go to file
2016-10-17 13:06:56 +02:00
bin html5tidy as proper tool 2016-01-15 14:08:09 +01:00
etherdump dump styles and versions script now parameterized to customize 2016-03-03 00:02:23 +01:00
.gitignore new things 2015-12-03 12:14:47 +01:00
LICENSE.txt added license document 2015-09-17 17:51:48 +02:00
padinfo.sample.json continued tweaks 2015-09-19 11:43:16 +02:00
README.md synced README with reality 2016-10-17 13:06:56 +02:00
setup.py subcommands 2015-09-17 18:23:18 +02:00

etherdump

Tool to publish etherpad pages to files.

Requirements

python-dateutil, html5lib

Installation

pip install python-dateutil html5lib
python setup.py install

Example

mkdir mydump
cd myddump
etherdump init

The program then interactively asks some questions:

Please type the URL of the etherpad: 
	http://automatist.local:9001/
The APIKEY is the contents of the file APIKEY.txt in the etherpad folder
Please paste the APIKEY: 
	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The settings are placed in a file called .etherdump/settings.json and are used (by default) by future commands.

subcommands

  • init
  • pull
  • 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)