Pumping pads as files into publishing frameworks!

6.5 KiB

Raw Blame History

etherpump

Pumping text from etherpads into publications

A command-line utility that extends the multi writing and publishing functionalities of the etherpad by exporting the pads in multiple formats.

Many pads, many networks

Etherpump is a fork of etherpump, a command line tool written by Michael Murtaugh that converts etherpad pages to files. This fork is made out of curiosities in the tool, a wish to study it and shared sparks of enthusiasm to use it in different situations within Varia.

Etherpump is a stretched version of etherpump. It is a playground in which we would like to add features to the initial tool that diffuse actions of dumping into pumping. So most of all, etherpump is a work-in-progress, exploring potential uses of etherpads to edit, structure and publish various types of content. Added features are:

opt-in publishing with the __PUBLISH__ magic word
the publication command, that listens to custom magic words such as __RELEARN__

See the Change log / notes section for further changes.

etherpump is a tool that is used from the command line. It dumps all pads of one etherpad installation to a folder, saving them as different text files, such as plain text and HTML. It also creates an index file, that allows one to easily navigate through the list of pads. etherpump follows a document-driven idea of publishing, which means that it converts pads as database entries into pads as files. This seems to be a redundant act of copying, but is actually an important in-between step that allows for many different publishing projects and experiments.

We started to get to know etherpump through various editions of Relearn and/or the worksessions organized by Constant. Collaborative writing on an etherpad has been an important ingredient for these situations. The habit of using pads branched into the day-to-day practice of Varia, where we use etherpads for all sorts of things, ranging from organising remote-meetings with 10+ people, to writing and designing PDF documents collaboratively.

After installing etherpump on the Varia server, we collectively decided to not want to publish pads by default. Discussions in the group around the use of etherpads, privacy and ideas of what publishing means, led to a need to have etherpump only start the indexing work after it recognizes a __PUBLISH__ marker on a pad. We decided to work on a __PUBLISH__ vs. __NOPUBLISH__ branch of etherpump, which we now fork into etherpump.

Change log / notes

October 2019

Improve etherpump --help handling to make it easier for new users.

Added the python-dateutil and pypandoc dependencies

Added a fancy progress bar with tqdm for long running etherpump pull --all calls

Started with the experimental library API.

September 2019

Forking etherpump into etherpump.

https://git.vvvvvvaria.org/varia/etherpump

Migrating the source code to Python 3.

Integrate PyPi publishing with setuptools.

May - September 2019

etherpump is used to produce the Ruminating Relearn section of the Network Of One's Own 2 (NOOO2) publication.

A new command is added to make a web publication, based on the custom magic word __RELEARN__.

June 2019

Multiple conversations around etherpump emerged during Relearn Curved in Varia, Rotterdam.

Including the idea of executable pads (etherhooks), custom magic words, a federated snippet protocol (etherstekje) and more.

https://varia.zone/relearn-2019.html

April 2019

Installation of etherpump on the Varia server.

https://etherpump.vvvvvvaria.org/

March 2019

The __PUBLISH__ vs. __NOPUBLISH__ was added to the etherpump repository by decentral1se.

https://gitlab.constantvzw.org/aa/etherpump/issues/3

Originally designed for use at: Constant.

More notes can be found in the git repository of etherdump.

Install etherpump

$ pip install etherpump

Etherpump only supports Python 3.

Command-line example

$ mkdir mydump
$ cd myddump
$ etherpump init

The program then interactively asks some questions:

Please type the URL of the etherpad: https://pad.vvvvvvaria.org/

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 .etherpump/settings.json and are used (by default) by future commands.

Library API Example

Etherpump can be used as a library. See etherpump/examples or read the short one below:

from etherpump.api import magicword

@magicword('__VARIA_PUB_CLUB__')
def maakt_niet_uit_wat_je_hier_schrijft(pads):
    print(pads['my-pad-name']['html'])

This is still a work in progress.

Subcommands

To see all available subcommands, run:

$ etherpump --help

For help on each individual subcommand, run:

$ etherpump revisionscount --help

Publishing

pip install twine
Bump the version number in etherpump/__init__.py following "semver" conventions
Run make publish

You should have a PyPi account and be added as an owner/maintainer on the etherpump package.

Maintenance utilities

Tools to help things stay tidy over time.

$ pip install flake8 isort black
$ make format
$ make lint

Please see the following links for further reading:

Keeping track of Etherpad-lite

License

GNU AFFERO GENERAL PUBLIC LICENSE, Version 3.

See LICENSE.txt.

6.5 KiB Raw Blame History