mirror of
				https://github.com/paperless-ngx/paperless-ngx.git
				synced 2025-10-30 03:56:23 -05:00 
			
		
		
		
	Merge branch 'main' into beta
This commit is contained in:
		| @@ -565,19 +565,15 @@ document. | ||||
|  | ||||
| ### Managing encryption {#encryption} | ||||
|  | ||||
| Documents can be stored in Paperless using GnuPG encryption. | ||||
|  | ||||
| !!! warning | ||||
|  | ||||
|     Encryption is deprecated since [paperless-ng 0.9](changelog.md#paperless-ng-090) and doesn't really | ||||
|     provide any additional security, since you have to store the passphrase | ||||
|     in a configuration file on the same system as the encrypted documents | ||||
|     for paperless to work. Furthermore, the entire text content of the | ||||
|     documents is stored plain in the database, even if your documents are | ||||
|     encrypted. Filenames are not encrypted as well. | ||||
|  | ||||
|     Also, the web server provides transparent access to your encrypted | ||||
|     documents. | ||||
|     Encryption was removed in [paperless-ng 0.9](changelog.md#paperless-ng-090) | ||||
|     because it did not really provide any additional security, the passphrase | ||||
|     was stored in a configuration file on the same system as the documents. | ||||
|     Furthermore, the entire text content of the documents is stored plain in | ||||
|     the database, even if your documents are encrypted. Filenames are not | ||||
|     encrypted as well. Finally, the web server provides transparent access to | ||||
|     your encrypted documents. | ||||
|  | ||||
|     Consider running paperless on an encrypted filesystem instead, which | ||||
|     will then at least provide security against physical hardware theft. | ||||
|   | ||||
| @@ -270,7 +270,7 @@ The following methods are supported: | ||||
| -   `remove_tag` | ||||
|     -   Requires `parameters`: `{ "tag": TAG_ID }` | ||||
| -   `modify_tags` | ||||
|     -   Requires `parameters`: `{ "add_tags": [LIST_OF_TAG_IDS] }` and / or `{ "remove_tags": [LIST_OF_TAG_IDS] }` | ||||
|     -   Requires `parameters`: `{ "add_tags": [LIST_OF_TAG_IDS] }` and `{ "remove_tags": [LIST_OF_TAG_IDS] }` | ||||
| -   `delete` | ||||
|     -   No `parameters` required | ||||
| -   `reprocess` | ||||
|   | ||||
| @@ -708,7 +708,8 @@ Paperless runs on Raspberry Pi. However, some things are rather slow on | ||||
| the Pi and configuring some options in paperless can help improve | ||||
| performance immensely: | ||||
|  | ||||
| -   Stick with SQLite to save some resources. | ||||
| -   Stick with SQLite to save some resources. See [troubleshooting](troubleshooting.md#log-reports-creating-paperlesstask-failed) | ||||
|     if you encounter issues with SQLite locking. | ||||
| -   If you do not need the filesystem-based consumer, consider disabling it | ||||
|     entirely by setting [`PAPERLESS_CONSUMER_DISABLE`](configuration.md#PAPERLESS_CONSUMER_DISABLE) to `true`. | ||||
| -   Consider setting [`PAPERLESS_OCR_PAGES`](configuration.md#PAPERLESS_OCR_PAGES) to 1, so that paperless will | ||||
|   | ||||
| @@ -292,7 +292,9 @@ many workers attempting to access the database simultaneously. | ||||
| Consider changing to the PostgreSQL database if you will be processing | ||||
| many documents at once often. Otherwise, try tweaking the | ||||
| [`PAPERLESS_DB_TIMEOUT`](configuration.md#PAPERLESS_DB_TIMEOUT) setting to allow more time for the database to | ||||
| unlock. This may have minor performance implications. | ||||
| unlock. Additionally, you can change your SQLite database to use ["Write-Ahead Logging"](https://sqlite.org/wal.html). | ||||
| These changes may have minor performance implications but can help | ||||
| prevent database locking issues. | ||||
|  | ||||
| ## granian fails to start with "is not a valid port number" | ||||
|  | ||||
|   | ||||
| @@ -211,7 +211,7 @@ class TestBulkEditAPI(DirectoriesMixin, APITestCase): | ||||
|     def test_api_modify_tags_not_provided(self, m): | ||||
|         """ | ||||
|         GIVEN: | ||||
|             - API data to modify tags is missing modify_tags field | ||||
|             - API data to modify tags is missing remove_tags field | ||||
|         WHEN: | ||||
|             - API to edit tags is called | ||||
|         THEN: | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 shamoon
					shamoon