mirror of
				https://github.com/paperless-ngx/paperless-ngx.git
				synced 2025-11-03 03:16:10 -06:00 
			
		
		
		
	Merge branch 'main' into beta
This commit is contained in:
		@@ -369,7 +369,7 @@ the naming scheme.
 | 
			
		||||
 | 
			
		||||
.. warning::
 | 
			
		||||
 | 
			
		||||
    Since this command moves you documents around alot, it is advised to to
 | 
			
		||||
    Since this command moves you documents around a lot, it is advised to to
 | 
			
		||||
    a backup before. The renaming logic is robust and will never overwrite
 | 
			
		||||
    or delete a file, but you can't ever be careful enough.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
@@ -243,7 +243,7 @@ will create a directory structure as follows:
 | 
			
		||||
    last filename a document was stored as. If you do rename a file, paperless will
 | 
			
		||||
    report your files as missing and won't be able to find them.
 | 
			
		||||
 | 
			
		||||
Paperless provides the following placeholders withing filenames:
 | 
			
		||||
Paperless provides the following placeholders within filenames:
 | 
			
		||||
 | 
			
		||||
* ``{asn}``: The archive serial number of the document, or "none".
 | 
			
		||||
* ``{correspondent}``: The name of the correspondent, or "none".
 | 
			
		||||
 
 | 
			
		||||
@@ -211,7 +211,7 @@ PAPERLESS_AUTO_LOGIN_USERNAME=<username>
 | 
			
		||||
PAPERLESS_ADMIN_USER=<username>
 | 
			
		||||
    If this environment variable is specified, Paperless automatically creates
 | 
			
		||||
    a superuser with the provided username at start. This is useful in cases
 | 
			
		||||
    where you can not run the `createsuperuser` command seperately, such as Kubernetes
 | 
			
		||||
    where you can not run the `createsuperuser` command separately, such as Kubernetes
 | 
			
		||||
    or AWS ECS.
 | 
			
		||||
 | 
			
		||||
    Requires `PAPERLESS_ADMIN_PASSWORD` to be set.
 | 
			
		||||
 
 | 
			
		||||
@@ -7,7 +7,7 @@ Frequently asked questions
 | 
			
		||||
 | 
			
		||||
**A:** While Paperless-ngx is already considered largely "feature-complete" it is a community-driven
 | 
			
		||||
project and development will be guided in this way. New features can be submitted via
 | 
			
		||||
GitHub discussions and "up-voted" by the community but this is not a garauntee the feature
 | 
			
		||||
GitHub discussions and "up-voted" by the community but this is not a guarantee the feature
 | 
			
		||||
will be implemented. This project will always be open to collaboration in the form of PRs,
 | 
			
		||||
ideas etc.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
@@ -62,7 +62,7 @@ your documents:
 | 
			
		||||
 | 
			
		||||
1.  OCR the document, if it has no text. Digital documents usually have text,
 | 
			
		||||
    and this step will be skipped for those documents.
 | 
			
		||||
2.  Paperless will create an archiveable PDF/A document from your document.
 | 
			
		||||
2.  Paperless will create an archivable PDF/A document from your document.
 | 
			
		||||
    If this document is coming from your scanner, it will have embedded selectable text.
 | 
			
		||||
3.  Paperless performs automatic matching of tags, correspondents and types on the
 | 
			
		||||
    document before storing it in the database.
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user