# ebookconverter code that orchestrates ebook conversion for project gutenberg
EbookConverter manages the creation and update of ebook assets for Project Gutenberg. It uses a postgres database to keep track of both ebook metadata and ebook files. the postgress database is managed by the libgutenberg package.
The cron-rebuild-files.sh script runs as a cron job, rebuilding 2100 books per day, so as to rebuild every book roughly once a month.
ebookconverter talks to the gutenberg database to build a list of ebookmaker jobs. These jobs require some metadata about the book, and a target file to process.
ebookconverter expects source files to be in numbered directories in a ‘files’ directory. The location of the files directory is given by the FILESDIR config parameter.
Config parameters should be set in a file at /etc/ebookconverter.conf or ~/.ebookconverter
ebookconverter has been tested on Python 3.9.
see the Ebookmaker Readme for system package dependencies: <https://github.com/gutenbergtools/ebookmaker/blob/master/README.md>
## Installing
pipenv install ebookconverter
- The following directories should exist:
$PRIVATE/logs
$PRIVATE/logs/json
$PRIVATE/logs/json/backup
$PRIVATE/logs/notifications
$PRIVATE/logs/dopush
$PRIVATE/logs/dopush/backup
## Using the EbookConverter Scripts
you can run these commands either by first entering a pipenv shell or on a single line using pipenv run <command> <args>
Rebuild one or more books ebookconverter –range=<start>-<finish> –build=all ebookconverter –range=<booknumber> –build=all ebookconverter –range=<booknumber> –build=all –validate
Reload metadata from a workflow json file (use with care, it will overwrite any metadata in the DB) reload_workflow <booknumber>
Regenerate the csv file make_csv
Look for any ebooks with changed files in the last X days and then check if any of the previously known files of that ebook have been deleted.
autodelete
Metadata
Release files for ebookconverter 0.11.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ebookconverter-0.11.5.tar.gz | 62.4 kB | Without provenance | Details for ebookconverter-0.11.5.tar.gz |
Release files / ebookconverter-0.11.5.tar.gz
| Download URL | ebookconverter-0.11.5.tar.gz |
|---|---|
| Size | 62.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
285157a956f72823003fc11305f848f58030af46d6b17f49df5a3dba034635b8
|
|
BLAKE2b-256 checksum How to use checksums |
9de94692d19faaf94aa7257de0972020984a4ac421bbd785e458a93d22eb38bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.11
|
Security for ebookconverter 0.11.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.