aboutsummaryrefslogtreecommitdiffstats
path: root/deskutils/py-paperless-ngx/files/pkg-message.in
blob: 7d159577cfd25747292451482ff8e14f77767d53 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
[
{ type: install
  message: <<EOM
  Please see `man paperless-ngx' for details on how to configure paperless.
EOM
}
{ type: upgrade
  message: <<EOM
After each upgrade, please check for differences between your config and
the sample configuration installed by the package:

    diff -u %%PREFIX%%/etc/paperless.conf \
           %%PREFIX%%/etc/paperless.conf.sample

Then merge in changes as required by editing
%%PREFIX%%/etc/paperless.conf.

Database migrations are run automatically on service start, but
it's recommended to run them explicitly, especially on major upgrades:

    service paperless-migrate onestart

EOM
}
{ type: upgrade
  maximum_version: "2.7.2_1"
  message: <<EOM
Configuration of NLTK data has been fixed in port version 2.7.2_1.

Please modify your %%PREFIX%%/etc/paperless.conf based on
`*NLTK*` settings found in %%PREFIX%%/etc/paperless.conf.sample.
EOM
}
{ type: upgrade
  minimum_version: "2.16.0"
  maximum_version: "2.17.1"
  message: <<EOM
WARNING

In versions 2.16.0 - 2.16.3, the interpretation of offset days for
scheduled workflows was inverted. This has  been corrected to restore
the intuitive, pre-2.16 behavior:

    Positive offsets now trigger workflows after the date
    Negative offsets trigger workflows before the date

If you configured scheduled workflows in v2.16.x with inverted offsets
(or adjusted a trigger created in 2.15.x), you must now adjust the
offset sign to match this corrected logic.

If you did not alter your workflow triggers after upgrading from v2.15,
no changes are required.
EOM
}
{ type: upgrade
  maximum_version: "2.18.2_2"
  message: <<EOM
Starting with version 2.18, paperless-ngx uses ES6 module files using
the file extension `mjs`. These need to be served using the media type
`text/javascript`.

See %%EXAMPLESDIR%%/nginx.conf for an example
of how this can be configured when using nginx.
EOM
}
]