On Sun, Jun 23, 2019 at 11:04:23PM +0000, John Rouillard wrote:
> The traceback error in the server log/emailed to the admin is:
...
> That at least makes the misconfig obvious.
> 
> I don't like it though. What I really want is the ability to get a
> secret key automatically generated when running roundup-admin with:

Yes, the value should somehow be set.

> >  2) That key should be set to a constant value when running:
> >
> >      roundup-admin -i . updateconfig config.ini
> >
> >     as specified in doc/upgrading.txt ...
> 
> My guess is you didn't run this and as a result have a hidden problem.

No, I didn't. And when grepping for secret_key in doc it didn't turn up
anything .-)

> 
> You suggested documenting this in the rest doc. Would adding something
> like this at the end of the "Enabling the REST API" section work:
> 
>   Make sure that config.ini has a secret_key option defined in the web
>   section of config.ini. If you followed the upgrading directions, it
>   is done automatically when running "roundup-admin ... updateconfig
>   config.ini". If you are installing a new tracker with "roundup-admin
>   ... install" the secret_key value is automatically set to some
>   random value. If this is not set, you will see different etag values
>   for the same unchanged item on each REST call.
> 
> I would prefer to document this and leve the existing code as is as I
> think it is more user friendly provided the update instructions to run
> "roundup-admin .... updateconfig" works.

Yes, I like the variant with the documentation. This proposal also takes
care about the grep for secret_key turning up something .-)

Thanks for looking into this

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com