Assist in organizing your piles of documents, resulting from scanners, e-mails and other sources with miminal effort.
🎉 Changelog • Documentation • Milestone 🎉
AddonExecutionResult monoid (#2363)session-valid values (#2309)flattenArchives is true (#2063)With the addition of khmer language, solr needs now to load its analysis-extra module. It is (usually) packaged with the solr distribution, so it only requires to change the startup command. The docker-compose file has been changed accordingly. You might need to check your setup.
The in-process database H2 was updated in this release: from 2.1.214 to 2.2.224. You need to migrate your data to make it work with the new release. Exporting using the old version and importing using the new version should work fine. For details, please refer to the h2 documentation. There is a script tools/h2-util.sh to help with this process. Also this comment might be useful.
🎉 Changelog • Documentation • Milestone 🎉
This release contains some bug fixes and improvements.
, to . for numeric fields (#1975)🎉 Changelog • Documentation • Milestone 🎉
This release contains some bug fixes, updates docker images and includes some internal change to get a bit forward with #585 (user groups).
weasyprint as an alternative to wkhtmltopdf for converting html files to pdfattach.count. It has been removed a while ago, but the query language didn't reflect it (#1758)Warning
The database structure changed substantially in this release. Please make sure to create a backup of your database before attempting the upgrade!
There are two major changes for docker users: First ARM7 support has been dropped, because it was too much work to maintain alongside the other architectures. Second the images have been updated to the latest alpine linux, which requires to sacrifice using wkhtmltopdf as a tool to convert HTML to PDF (often used for processing emails).
The joex image doesn't have the wkhtmltopdf binary anymore, because it is not available for alpine linux. Instead weasyprint has been added. Docspell by default still uses wkhtmltopdf, because I found it has better results. But you can now switch to weasyprint and if you use the provided docker images you have to.
There is a new config that you need to set - when using environment variables:
DOCSPELL_JOEX_CONVERT_HTML__CONVERTER=weasyprint
Just add it to the env variables in the docker-compose.yml. If you use a config file, add this to it:
docspell.joex {
convert.html-converter = "weasyprint"
}
The internal change on how collectives are now referenced requires to adopt the files accordingly. If you have your files in the database, all is being migrated automatically on first start.
For other file backends, the files must be migrated manually. The difference is that from now on a collective is referenced by a unique number and not by its name anymore. You can look at the table collective to see which number was assigned to a collective and then
If you use H2 as a database, there are some manual steps required. H2 was bumped from 1.4.x to 2.1.x and the new version cannot read the database files of the old version.
Additionally, one of the changesets for H2 used a now illegal syntax and had to be changed. This will lead to checksum mismatch errors when starting up.
Creating and restoring a dump, the script tools/h2-util.sh can be used. The H2 version can be specified with an environment variable H2_VERSION to easily create a dump in one version and restore in another.
To fix the changeset, you could simply run this sed command on the dump before restoring:
sed -i 's,175554607,-276220379,g' docspell-dump-h2.sql
But this could potentially change not only the checksum, but other things in the dump. It is not very likely, though. A more safe alternative is to use a text editor and find the correct place (in table flyway_schema_history) to change or just set database-schema.repair-schema = true in the config file or use the env variables
DOCSPELL_SERVER_BACKEND_DATABASE__SCHEMA_REPAIR__SCHEMA=true
and startup only the restserver one time to have the checksum fixed. Another safe variant is to run this update statement on your h2 database:
UPDATE flyway_schema_history set checksum = -276220379 WHERE version = '1.9.3';
🎉 Changelog • Documentation • Milestone 🎉
This release fixes some issues related to OpenID connect integration and addons.
🎉 Changelog • Documentation • Milestone 🎉
This is more a bug fix release, targeting mainly fixes related to addons.
🎉 Changelog • Documentation • Milestone 🎉
This release allows to extend Docspell with custom scripts/programs. This is still an experimental feature, I expect more changes coming. But you are invited to give it a try 😄!
Note to docker users: The docker image of the previous release contained a "broken" zlib library that affected checksum generation for the db migrations (see #1517). The image of this release has an updated version of this system library. This means that it is quite likely that those who were not affected by this in 0.35.0 (for example, you started with a fresh db) - could now be affected. If you get these errors, try to "repair" the migrations. Apply the following settings in the docker-compose file for one start:
DOCSPELL_SERVER_BACKEND_DATABASE__SCHEMA_REPAIR__SCHEMA=true
DOCSPELL_SERVER_BACKEND_DATABASE__SCHEMA_RUN__FIXUP__MIGRATIONS=true
DOCSPELL_SERVER_BACKEND_DATABASE__SCHEMA_RUN__MAIN__MIGRATIONS=true
Start up one time and stop again. Then remove these settings again.
🎉 Changelog • Documentation • Milestone 🎉
🎉 Changelog • Documentation • Milestone 🎉
For some of the new features, you need the new version of dsc.
🎉 Changelog • Documentation • Milestone 🎉
| ⚠️ Important |
|---|
| Unfortunately, this release contains a DB migration script that fails on some installations. It can be sorted out by following the guide in #1436 and requires to connect to the DB directly. If you don't want to run commands against the database, you can wait for the next release. |
logback.xml before, I'm sorry this is not possible anymore. There are two settings in the config file for now to control logging: logging.minimum-level and logging.format.src attribute of the embed element changesiframe is now used - thus for mobile it should work now. Safari on desktop would require to change the respective setting