Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove logo backup instructions #188

Merged
merged 1 commit into from
Apr 4, 2021
Merged

Remove logo backup instructions #188

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 0 additions & 24 deletions docs/backup_and_restore.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,24 +104,6 @@ archive in the output of the backup command.

.. include:: includes/backup-warning.txt

.. _backing_up_logos:

Backing up your custom logo
'''''''''''''''''''''''''''

The backup will not include any custom logo file that you have configured
for your SecureDrop instance. To back up your logo:

1. Open a terminal via **Applications ▸ System Tools ▸ Terminal**.
2. Change into the persistent storage directory: ``cd ~/Persistent``
3. Run the following command:

.. code:: sh

wget $(grep Exec ~/source.desktop | awk '{print $2}')/org-logo -O logo-backup.png

This will save your current logo file as ``logo-backup.png``.

Restoring from a Backup
-----------------------

Expand Down Expand Up @@ -356,9 +338,6 @@ Migrating Using a V2+V3 or V3-Only Backup
#. :doc:`Test the new instance <test_the_installation>` to verify that the
web interfaces are available and the servers can be reached via SSH.

#. If you had previously configured a custom logo for your SecureDrop instance,
:ref:`upload it again <Updating Logo Image>` using the *Admin Interface*.

#. If you have migrated to new hardware, ensure your old servers have been
decommissioned and/or destroyed by following the relevant sections of
:doc:`our decommissioning documentation <decommission>`.
Expand Down Expand Up @@ -578,9 +557,6 @@ source accounts, and journalist accounts. To do so, follow the steps below:
*Admin Workstations* will be out of date, and will need to be
:ref:`updated <update_tails_v3>`.

#. If you had previously configured a custom logo for your SecureDrop instance,
:ref:`upload it again <Updating Logo Image>` using the *Admin Interface*.

#. If you have migrated to new hardware, ensure your old servers have been
decommissioned and/or destroyed by following the relevant sections of
:doc:`our decommissioning documentation <decommission>`.
Expand Down
2 changes: 0 additions & 2 deletions docs/upgrade/focal_migration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,8 +210,6 @@ you have completed the :ref:`preparatory steps <focal_prep>`.
#. Announce your maintenance window. As part of this procedure, your servers
will become unreachable.
#. :doc:`Take a backup of the current instance <../backup_and_restore>`.
If you have configured a custom logo for your SecureDrop instance, make
sure to :ref:`download it <backing_up_logos>` as well.

Once you have taken a backup of the servers, power them off.

Expand Down