paradizelost/paperless-ngx
1
0
Fork 0
mirror of https://github.com/paperless-ngx/paperless-ngx.git synced 2025-04-02 13:45:10 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #322 from paperless-ngx/fix-sphinx-errors

Browse Source 
Fix minor sphinx errors
This commit is contained in:
shamoon 2022-03-14 06:49:25 -07:00 committed by GitHub
commit 9d9789953b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/administration.rst
View File

@ -379,7 +379,7 @@ the naming scheme.
The command takes no arguments and processes all your documents at once. The command takes no arguments and processes all your documents at once.
Learn how to use :ref:`Management Utilities<Management utilities>`. Learn how to use :ref:`Management Utilities<utilities-management-commands>`.
.. _utilities-sanity-checker: .. _utilities-sanity-checker:

15
docs/advanced_usage.rst
View File

@ -179,13 +179,14 @@ Assumed you have ``/home/foo/paperless-ngx/scripts/post-consumption-example.sh``
You can pass that script into the consumer container via a host mount in your ``docker-compose.yml``. You can pass that script into the consumer container via a host mount in your ``docker-compose.yml``.
.. code:: bash .. code:: bash
...
consumer: ...
... consumer:
volumes: ...
... volumes:
- /home/paperless-ngx/scripts:/path/in/container/scripts/ ...
... - /home/paperless-ngx/scripts:/path/in/container/scripts/
...
Example (docker-compose.yml): ``- /home/foo/paperless-ngx/scripts:/usr/src/paperless/scripts`` Example (docker-compose.yml): ``- /home/foo/paperless-ngx/scripts:/usr/src/paperless/scripts``

2
docs/extending.rst
View File

@ -115,7 +115,7 @@ Testing and code style:
configuration. This is not ideal. But for now, make sure no settings except for DEBUG are overridden when testing. configuration. This is not ideal. But for now, make sure no settings except for DEBUG are overridden when testing.
* Coding style is enforced by the Git pre-commit hooks. These will ensure your code is formatted and do some * Coding style is enforced by the Git pre-commit hooks. These will ensure your code is formatted and do some
linting when you do a `git commit`. linting when you do a `git commit`.
* You can also run ``black`` manually to format your code * You can also run ``black`` manually to format your code
.. note:: .. note::