clippingkeeper stores all your web "clippings" (title, url, text) in a database for later retrieval. I wrote it to reliably store weblog entries and other web pages for later use in my own "list of..." weblog entries.
clippingkeeper uses a Python cgi script to store and view the entries. To use clippingkeeper, you must have a web server capable of calling Python version 2.4 scripts, and a PostGreSQL database accessible to the web server.
Expat License, AKA MIT License.
- Modify clippingkeeper.example.cfg to suit your web server (cgiurl), database ([db] section), and personal tastes ([categories] section).
- Save clippingkeeper.example.cfg as clippingkeeper.cfg (i.e. remove the ".example" from the name).
- Run clippingkeeper.postgresql.sql on your database to create the ckentries table. A convenience script, deploy.pgsql.example.bsh, is included. Modify the capitalized arguments as necessary.
- Copy the following to the cgi-bin/ directory of your chosen web server:
- Test clippingkeeper by calling it with no arguments (i.e. http://yourhost/cgi-bin/clippingkeeper.py). You should see the main page ("Add an entry").
- Add an entry.
- View the entries.
- When you want to set some entries as used, meaning you want to publish them somewhere else and no longer see them in the "new" view, select them from the "view new" link. Another page will appear, with those links in a textbox, ready for copying.
The entries will appear as a list in the selected format (ReST format, or HTML anchors).
clippingkeeper will not delete the entries immediately; you must go to the admin page and flush the table to permanently delete the entries.
- add user-selected output format
- add deletion of isnew=0 records