Conor Schaefer

+1 on having the service log directly from systemd, that would greatly simplify the current logging logic. Not sure what's meant by `StreamHandler` and `argparse` in the context of logging,...

Looks like this will entail a bit of templatizing, since the db values are currently read from `config.ini`, but the values in that file are not written by Ansible.

Also, it appears that the db connector logic in `database.py` is defaulting to using the test database, which isn't correct for actual use of the crawlers running in prod.

Since we're not just running a single service, and we want to carefully control which script runs when, maybe we should simply use cron to manage the script runs and...

@ageis Not a bad idea. I'd merge a PR that makes the entire build command a var, preserves its current default behavior, but lets folks override it with something else....

Certainly not a blocker, and maybe not even worth paying extra for (although we're using a lot of CircleCI across our various repos now), but workflows do provide better feedback...

> The old securedrop.org has some local plugin handling captcha validation logic Good distinction: we should definitely strive for a no-third-parties approach here. This one _looks_ like it'd fit the...

We definitely did update the URL, but I agree the behavior looks like the network call failed.

Thanks for opening, @harrislapiroff. Yes, removing the dead codepaths relating to external accounts for SecureDrop Administrators sounds like the right thing to do at this point in time. We're not...

Observed this in the wild today, recommended as a workaround: `qvm-volume resize sd-large-buster-template:root 15G`.