Martin
Martin
See https://github.com/freedomofpress/securedrop/pull/7606#issuecomment-3542424304 for the latest overview of fresh installation and upgrading/migrating for existing users.
From https://github.com/freedomofpress/securedrop/pull/7606#issuecomment-3542424304: > Manual updates are straightforward: Check out the release tag with the debian packaging changes run `./securedrop-admin setup`, which does much the same as above except for not...
Another Q: From the current Admin Workstation install docs: > Next, run the configuration playbook and answer the prompts with values that match your environment: `./securedrop-admin sdconfig` > The script...
Similarly, are the onion service files still saved there? Basically are the Ansible paths unchanged? Or moved to the new config dir?
Ah, is it all here: `/usr/share/securedrop-admin/ansible-base/` ?
Yeah I've got the change to the `securedrop-admin` command, I was just quoting the current docs. Thanks for the paths clarification, I think I've got it now.
Here's a more fun docs question: For an initial fresh install, should the git repo be cloned to `~/Persistent`? After the successful installation of the deb package `securedrop-admin` I don't...
Are there new instructions for ["Troubleshooting Workstation Updates"](https://docs.securedrop.org/en/stable/admin/maintenance/update_workstations.html), beyond the specific case of `2.12.10` -> `2.13.0`? How will updates be done manually post 2.13.0?
There are few places in the docs where we ask a user to check the current installed version of `securedrop-admin`. Will the new `securedrop-admin` package self-report the installed version (e.g....
I've stepped through the QA upgrade scenario for RC1 and it looks good on my end!