Dokang

Latest version: v0.10.1

Safety actively analyzes 626691 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

0.9.1

------------------

- Fix packaging

0.9.0

------------------

- Allow running simultaneous threads of Dokang web application.

Until now, Dokang updated its list of document sets at startup and
when a new document set was uploaded. Running multiple threads of
the web application was obviously not working great, as one thread
would not see any new document set if it was added by another
thread.

This limitation has now been lifted and Dokang web application can
run with multiple threads (for example with multiple uWSGI workers).

0.8.2

-------------------------

- Update doc set title after uploading a new version of the documentation.

0.8.1

-------------------------

- Fix packaging.

0.8.0

-------------------------

- Use the title of the index page as the title of each doc set.
- Group doc sets by the first letter of their title.

0.7.0

-------------------------

- Add support of Python 3.5.

- When initializing the index, ``dokang init`` now creates all needed
intermediate-level directories.

- Add purge option to ``dokang clear`` to delete uploaded files.

- Fix change detection: we used to store and use the modification time
of the files. We now compute and store an MD5 hash for each file. It
is slower than getting the modification time, but it handles more
use cases.

**This is a backward-incompatible change.** You must reindex all
documents, like this::

dokang init --force
dokang index

- Remove bogus indexation optimization. The indexation should be a lot
faster now, especially on large document base.

- Fix encoding error when parsing non ASCII, non UTF-8 HTML files.
UTF-8 files were correctly processed, though.

- Add basic support for OpenSearch.

- Exclude more Sphinx-generated files like ``objects.inv`` and
``searchindex.js``.

- Display path of files in the search results of the command line
client.

- Fix bug in document deletion. When a document was detected as
deleted from a document set (i.e. when a file was not present
anymore in the "upload" directory), the indexation process deleted
from the index *all* documents with the same path (for example
``index.html``) in *all* document sets. The files themselves were
not deleted so the next indexation would add them back to the index.

- Use an asynchronous index writer that allows multiple indexation to
be done concurrently. Without this, a ``whoosh.index.LockError``
exception is raised.

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.