bernat at debian.org
Wed Oct 14 07:44:26 UTC 2015
❦ 14 octobre 2015 08:27 +0200, Jonas Genannt <jonas at brachium-system.net> :
>> Upstream is working on making the tests succeed even when Flask-Cache
>> is not present (we don't have it in Debian), hence the override for
>> dh_auto_test. The NEW queue taking currenly some time, I don't plan to
>> package flask-cache just yet.
>> I am reusing the _graphite user (adduser will ensure that it has the
>> appropriate properties when it exists, hence not checking with
>> getent). Logs are put in /var/log/graphite-api and there is
>> /var/lib/graphite-api whose sole purpose is to receive the index. I
>> could move it to /var/lib/graphite but then the API needs to have the
>> rights to write here the first time. The index could be created in
> The index is the same as in Graphite? - I shipping a cronjob that
> rebuilds the index every hour.
I don't know if the index is the same. Upstream told me a cronjob is
useless (I have assumed it is useless for graphite-api). I'll ask.
If the index is the same, it seems still easier to have a different
file. Otherwise, purging becomes difficult to handle.
>> I did just test that it builds, installs and runs.
>> Tell me if you see anything wrong.
> Seems very good. At some point I will add a sample Apache WSGI
> Configuration if you don't mind.
Of course, NP.
Grief can take care of itself; but to get the full value of a joy you must
have somebody to divide it with.
-- Mark Twain
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 818 bytes
Desc: not available
More information about the Pkg-graphite-maint