Bug#932484: isso gives 404 when started via systemd

2019-11-22 Thread Jelmer Vernooij
That sounds great. On 22 November 2019 08:27:12 GMT-08:00, Jonathan Watt wrote: >Perhaps it would be best to have separate 'isso' and 'isso-multi' >systemd units? > >Additionally, is there somewhere that documents setting up Isso with >the current >unit? I guess maybe the man page (although that

Bug#932484: isso gives 404 when started via systemd

2019-11-22 Thread Jonathan Watt
Perhaps it would be best to have separate 'isso' and 'isso-multi' systemd units? Additionally, is there somewhere that documents setting up Isso with the current unit? I guess maybe the man page (although that doesn't really contain anything useful right now)? How would I go about submitting

Bug#932484: isso gives 404 when started via systemd

2019-11-22 Thread Jonathan Watt
Ignore what I said previously. I believe I've figured out why both Tiger!P and I have been having problems. I had assumed isso would be set up for normal use. However, it appears that the systemd unit is set up for the "Multiple Sites" method documented here:

Bug#932484: isso gives 404 when started via systemd

2019-11-20 Thread Jonathan Watt
The fix seems to be trivial. I changed the arguments passed to gunicorn3 to be as recommended on the official Isso docs for gunicorn here: https://posativ.org/isso/docs/extras/deployment/#gunicorn Specifically, I changed the ExecStart line in isso.service to the following:

Bug#932484: isso gives 404 when started via systemd

2019-07-19 Thread Tiger!P
Package: isso Version: 0.12.2-2 Severity: important Dear Maintainer, * What led up to the situation? I tried to use isso by starting is via systemd. * What exactly did you do (or not do) that was effective (or ineffective)? I started isso via systemd (systemctl start isso) which then