Releases: digitalevidencetoolkit/deptoolkit
0.11.0
What's Changed
The Toolkit now support S3-class storage options, both as a destintion to write data and as a store to consume data from.
If enabled, receiving an archive request (e.g. from the browser extension) will trigger its duplicated storage on S3 (in addition to locally). By default, the example webapp UI will attempt to surface archive thumbnails from S3.
- Store: S3 as a valid data source by @basilesimon in #75
- Store: S3 as a valid data destination by @basilesimon in #78
Full Changelog: 0.10.4...0.11.0
0.10.4
What's Changed
- Fix occasional catastrophic failure on fetching history (fix #67) by @basilesimon in #74
- Better handle long domain names by truncating them, e.g.
superlongdomai...
- Bump nanoid from 3.1.25 to 3.2.0 in /ui by @dependabot in #72
- Bump node-fetch from 2.6.1 to 3.1.1 by @dependabot in #73
Full Changelog: 0.10.3...0.10.4
0.10.3
This releases moves the project's recommended (er, enforced?) runtimes to the new node
LTS version (v16).
0.10.2
Minor changes
• 💅 The companion webapp implementing the API routes received a complete makeover
• 🛠 In local dev mode, the server
and ui
scripts now run in parallel and terminate as you'd expect on Ctrl+C
0.10.0
Major change: new Docker architecture
The new docker-compose
structure sets up two services: the API and the UI. The latter, which used to be a running npm
script, is now an Nginx webserver serving files resulting from the Svelte build.
API requests are now proxied from the UI. No need to call localhost:3000/endpoint
– the UI can reach the API at /api/endpoint
, thus facilitating future set up of a hosted service at a custom URL.
We're now relying on the presence of an .env
file including some details about the ledger. See "Environment" in the documentation
Minor changes
• Unit tests for the Verify module. Another upstream change improved the handling of nulls
and with this added strictness the Verify functions were refactored a bit so the returns would be more in line with expectations, i.e. a 404 for not found and a 200 for a match. see commit
• Unit tests and refactor of the Store module, notably so a configuration object is passed around to define where should data be stored (presently: only at a local path). see commit
• Refactor handling of file extensions: File.FileName()
helps us handle the different file extensions we're supporting, i.e. HTML, PNG. see commit
0.9.0
0.8.0
• Support the verification of an archive (i.e. a bunch of files), which the user drag-and-drops into the UI
• Support the export of working copies, identical to the originals, as a ZIP file
• Include a new UI powered by Sveltekit, with filesystem-based routing
• Surface a prettier history of a record's life (edits, exports, etc.), with a small chart
• Include the browser extension in the monorepo
0.5.0
• Support revision/updating of a record: users can now add a full-text description to an inscription
• UI improvements, with the inclusion of Attractions, “a pretty cool UI kit for Svelte.”
0.4.1
• Surface history of a ledger inscription, setting the scene for more
0.4.0
• Include a SingleFile-like .html
into the Bundle
.
• Show presence of these archives in the Svelte app
• See the implementation in the Firefox extension