Update docs to include instructions for unattended-upgrades under Ubuntu Focal #146
Conversation
There was a problem hiding this comment.
LGTM based on visual review. I left one small comment but it's not a showstopper. Thanks @emkll :)
(Making a mental note: reviewing this PR made me re-read the "Partitioning the disks" section of the install docs, and maybe we should simplify that section just to say "don't enable FDE." The way we currently word it, introduce FDE, and then strongly recommend not to use it is a bit confusing. If others agree, I'll open an issue. However, I think that's out of scope for this PR).
docs/admin.rst
Outdated
| and you are using SSH-over-Tor), your SSH connection may be interrupted, and you | ||
| SecureDrop will update and reboot once per day. However, once a SecureDrop | ||
| update `is announced`_ , you can opt to fetch the update immediately. Depending | ||
| on the nature of the update (e.g., if the ``tor`` package is upgraded and you are |
There was a problem hiding this comment.
(Nit) for clarity's sake, I would move the "Depending on the nature of the update, ..." sentence to the very end of these instructions (current line 451), optionally in a note. But I don't think it's worth doing unless other people request other changes as well.
Starting with Ubuntu 20.04, we plan on using unattended-upgrades instead of cron-apt.
emkll
force-pushed
the
5295-unattended-upgrades
branch
from
7afb939
to
fba36b5
Compare
|
freedomofpress/securedrop#5684 has been merged, rebased on latest |
Status
Ready for review
Description of Changes
Testing
Instructions are logical and manual upgrade logic works in both Xenial (cron-apt) and Focal (unattended-upgrades)
Release
Checklist (Optional)
make docs-lint) passed locallymake docs-linkcheck) passedmake docs) docs at http://localhost:8000