From 62da1f49ae07541a19d6db76a6cf275e6ef975b7 Mon Sep 17 00:00:00 2001 From: Daniel Quinn Date: Mon, 28 Mar 2016 19:58:29 +0100 Subject: [PATCH] Added not about paperless.conf --- docs/migrating.rst | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/migrating.rst b/docs/migrating.rst index d659620ac..04690f66b 100644 --- a/docs/migrating.rst +++ b/docs/migrating.rst @@ -73,10 +73,10 @@ immediately start consuming the documents. Updates ------- -For the most part, all you have to do to update *Paperless* is run ``git pull`` -on the directory containing the project files, and then use Django's ``migrate`` -command to execute any database schema updates that might have been rolled in -as part of the update: +For the most part, all you have to do to update Paperless is run ``git pull`` +on the directory containing the project files, and then use Django's +``migrate`` command to execute any database schema updates that might have been +rolled in as part of the update: .. code-block:: shell-session @@ -88,6 +88,11 @@ as part of the update: Note that it's possible (even likely) that while ``git pull`` may update some files, the ``migrate`` step may not update anything. This is totally normal. +Additionally, as new features are added, the ability to control those features +is typically added by way of an environment variable set in ``paperless.conf``. +You may want to take a look at the ``paperless.conf.example`` file to see if +there's anything new in there compared to what you've got int ``/etc``. + If you are :ref:`using Docker ` the update process requires only one additional step: