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.

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

Updates recommended hostnames for Qubes staging #150

Merged
merged 1 commit into from
Feb 11, 2021
Merged
Changes from all commits
Commits
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
6 changes: 2 additions & 4 deletions docs/development/qubes_staging.rst
Original file line number Diff line number Diff line change
Expand Up @@ -161,11 +161,9 @@ on your OS choice:
- **Focal:** In the console for each machine, edit ``/etc/netplan/00-installer-config.yaml`` to update the ``addresses`` entry with the machine's IP.

Edit ``/etc/hosts`` on each host to include the hostname and IP for itself.
Use ``sd-staging-app`` and ``sd-staging-mon``, omitting the ``-base-$SERVER_OS`` suffix, since the cloned VMs
will not have the suffix.
Use ``app-staging`` and ``mon-staging`` as appropriate.

Next, on each host edit ``/etc/hostname`` to reflect the machine's name.
Again, omit the ``-base-SERVER_OS`` suffix.

Halt each machine, then restart each from ``dom0``. The prompt in each console
should reflect the correct name of the VM. Confirm you have network access by
Expand Down Expand Up @@ -312,7 +310,7 @@ the Makefile target:
.. code:: sh

molecule create -s qubes-staging-$SERVER_OS
molecule converge -s qubes-staging-#SERVER_OS
molecule converge -s qubes-staging-$SERVER_OS
molecule test -s qubes-staging-$SERVER_OS

That's it. You should now have a running, configured SecureDrop staging instance
Expand Down