Scan, index, and archive all of your paper documents
psycopg2
to the Pipfile #489. He also fixed a syntax error in docker-compose.yml.example
#488 and added DjangoQL, which allows a litany of handy search functionality #492.DEBUG
value. The paperless.conf.example
file was also updated to mirror the project defaults.RecentCorrespondentsFilter
correspondents filter that was added in 2.4 to play nice with the defaults. Thanks to @tsia and @Sblop who pointed this out. #423..editorconfig
file to better specify coding style.PAPERLESS_OPTIPNG_BINARY
. The Docker image has already been updated on the Docker Hub, so you just need to pull the latest one from there if you're a Docker user.slugify()
function. The slug value is still visible in the admin though..slug
values to ones conforming to the slugify()
rules..save()
in determining a slug and using that to check for an existing tag/correspondent.get_date()
functionality of the parsers has been consolidated onto the DocumentParser
class since much of that code was redundant anyway.unencrypted
, since exports are by their nature unencrypted. It's now in the import step that we decide the storage type. This allows you to export from an encrypted system and import into an unencrypted one, or vice-versa.PAPERLESS_DBUSER
in your environment. This will attempt to connect to your Postgres database without a password unless you also set PAPERLESS_DBPASS
.DISABLE_LOGIN
feature.@elohmeier added three simple features that make Paperless a lot more user (and developer) friendly:
You now also have the ability to customise the interface to your heart's content by creating a file called overrides.css
and/or overrides.js
in the root of your media directory. Thanks to @SummittDweller for this idea: #371.
This is a big release as we’ve changed a core-functionality of Paperless: we no longer encrypt files with GPG by default.
The reasons for this are many, but it boils down to that the encryption wasn’t really all that useful, as files on-disk were still accessible so long as you had the key, and the key was most typically stored in the config file. In other words, your files are only as safe as the paperless
user is. In addition to that, the contents of the documents were never encrypted, so important numbers etc. were always accessible simply by querying the database. Still, it was better than nothing, but the consensus from users appears to be that it was more an annoyance than anything else, so this feature is now turned off unless you explicitly set a passphrase in your config file.
Encryption isn’t gone, it’s just off for new users. So long as you have PAPERLESS_PASSPHRASE
set in your config or your environment, Paperless should continue to operate as it always has. If however, you want to drop encryption too, you only need to do two things:
./manage.py migrate && ./manage.py change_storage_type gpg unencrypted
. This will go through your entire database and Decrypt All The Things.PAPERLESS_PASSPHRASE
from your paperless.conf
file, or simply stop declaring it in your environment.Special thanks to @erikarvstedt, @matthewmoto, and @mcronce who did the bulk of the work on this big change.
PAPERLESS_DISABLE_LOGIN="true"
in your environment or in /etc/paperless.conf
.convert
and unpaper
and fail-out nicely.