Start9/documentation
2
0
Fork 0
mirror of https://github.com/Start9Labs/documentation.git synced 2026-03-26 02:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update various docs details (#396)

Browse Source 
* Various docs deficiencies brought up recently

* post-'embassy' Migration guide touchups

* post-'embassy' Migration guide touchups part 2

* post-'embassy' Migration guide touchups part 3
This commit is contained in:
gStart9
2023-06-05 15:13:17 +00:00
committed by GitHub
parent a5acc06a5f
commit 705812a6ff
4 changed files with 27 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
site/source/user-manual/connecting/connecting-lan/lan-os/lan-linux.rst
View File

@@ -77,10 +77,20 @@ Here we will insert your Start9 server's CA certificate into Linux's trust store
.. group-tab:: CentOS/Fedora
First, ensure mDNS resolution is turned on so you can reach your server:
Ensure ``MulticastDNS=Yes`` is set in /etc/systemd/resolved.conf and then restart systemd-resolved:
.. code-block:: bash
sudo systemctl restart systemd-resolved
Trust your server's CA certificate:
From the folder you have downloaded your Start9 server's Root CA, run the following commands (if you have changed the certificate's filename, be sure to change it here):
.. code-block:: bash
sudo yum install ca-certificates
sudo cp "<custom-address>.crt" /etc/pki/ca-trust/source/anchors/
sudo update-ca-trust

2
site/source/user-manual/connecting/connecting-tor/tor-firefox/torff-android.rst
View File

@@ -34,7 +34,7 @@ Once Tor is setup on your system, you can proceed to setup Firefox:
.. figure:: /_static/images/tor/storage-scopes-proxy.jpg
:width: 30%
#. (All users): Search for ``network.proxy.autoconfig_url``, and set the value to ``file:///storage/emulated/0/Download/proxy.pac``.
#. (All users): Search for ``network.proxy.autoconfig_url``, and set the value to ``file:///storage/emulated/0/Download/proxy.pac``. This is the default location of a the proxy.pac file downloaded in step 2, although your path may vary.
.. figure:: /_static/images/tor/autoconfig_url.png
:width: 50%

4
site/source/user-manual/connecting/connecting-tor/tor-firefox/torff-ios.rst
View File

@@ -5,8 +5,8 @@ Configuring Firefox for Tor on iOS
==================================
.. caution::
This guide assumes you have completed :ref:`setting up Tor for iOS<tor-ios>`. Please visit this section before proceeding as it is required for any regular browser such as Firefox to properly work with Tor.
This guide assumes you have completed :ref:`setting up Tor for iOS<tor-ios>`. Please visit this section before proceeding as it is required for any browser in iOS to work with Tor.
Once Orbot is setup on your system as illustrated at the link above, you don't need to do anything special to have firefox or any other browser proxied via tor. It should just work for any given onion url.
Once Orbot is setup on your system as illustrated at the link above, you don't need to do anything special to have any browser proxied via tor. All browsers in iOS are Safari under the hood, and the way we've configured Orbot makes it so any browser will work for any given onion url, and won't use Tor for regular clearnet requests.

26
site/source/user-manual/service-guides/bitcoin/blockchain-copy.rst
View File

@@ -13,17 +13,17 @@ Blockchain Migration
If you have already synced the Bitcoin blockchain to the tip on one server, and would like to skip IBD on another server, follow this guide.
.. note:: The following guide requires that you have already :ref:`setup SSH on both Start9 servers<ssh>`.
In this guide, we will refer to your synced server as example-A.local and the server with no Bitcoin synced as example-B.local. Of course, please replace AAAAAAA and BBBBBBB with your appropriate Start9 servers' names.
In this guide, we will refer to your synced server as example-aaa.local and the server with no Bitcoin synced as example-bbb.local. Of course, please replace example-aaa and example-bbb with your corresponding Start9 servers' unique `adjective-noun` names.
**Install but don't start Bitcoin Core on the blockchain-less server**
#. Log into `https://example-B.local` and install Bitcoin Core (**Marketplace > Bitcoin > Bitcoin Core > Install**). Do *NOT* yet **CONFIGURE** or **START** Bitcoin Core.
#. Log into `https://example-bbb.local` and install Bitcoin Core (**Marketplace > Bitcoin > Bitcoin Core > Install**). Do *NOT* yet **CONFIGURE** or **START** Bitcoin Core.
**Prep your server with the synced blockchain**
#. Stop the Bitcoin Core service on `https://example-A.local` (**Services > Bitcoin Core > Stop**)
#. Stop the Bitcoin Core service on `https://example-aaa.local` (**Services > Bitcoin Core > Stop**)
#. :ref:`Open an ssh session <connecting-via-ssh>` to example-A.local
#. :ref:`Open an ssh session <connecting-via-ssh>` to example-aaa.local
#. Once at the shell, perform the following commands
@@ -31,30 +31,30 @@ If you have already synced the Bitcoin blockchain to the tip on one server, and
sudo -i
mkdir -m 0700 -p .ssh
ssh-keygen -t ed25519 -N '' -f .ssh/example-b.key
chmod 600 .ssh/example-b.key*
cat .ssh/example-b.key.pub
ssh-keygen -t ed25519 -N '' -f .ssh/example-bbb.key
chmod 600 .ssh/example-bbb.key*
cat .ssh/example-bbb.key.pub
#. Copy the output from the cat command into example-B's **System > SSH > Add New Key** text field:
#. Copy the output from the cat command into example-bbb's **System > SSH > Add New Key** text field:
.. figure:: /_static/images/walkthrough/ssh_key_add.jpg
#. Back on the shell of example-A.local, do the following (don't forget to replace example-B.local in the rsync command before you perform it):
#. Back on the shell of example-aaa.local, do the following (don't forget to replace example-bbb in the rsync command below before you perform it):
.. code-block:: bash
cd /embassy-data/package-data/volumes/bitcoind/data/main/
rsync -e "ssh -i ~/.ssh/example-b.key" -povgr --append-verify --rsync-path="sudo mkdir -p /embassy-data/package-data/volumes/bitcoind/data/main ; sudo rsync" ./{blocks,chainstate} start9@example-B.local:/embassy-data/package-data/volumes/bitcoind/data/main/
rsync -e "ssh -i ~/.ssh/example-bbb.key" -povgr --append-verify --rsync-path="sudo mkdir -p /embassy-data/package-data/volumes/bitcoind/data/main ; sudo rsync" ./{blocks,chainstate} start9@example-bbb.local:/embassy-data/package-data/volumes/bitcoind/data/main/
#. Wait some hours until the copy is complete. On a gigabit network, the limiting factor will be the write speed of your SSD on the receiving server. When it is complete, clean up a bit:
.. code-block:: bash
rm .ssh/example-b.key*
rm .ssh/example-bbb.key*
exit
#. Switch back to `https://example-B.local`, selecting **Services > Bitcoin Core**, **CONFIGURE**, configure it as desired, **SAVE** and then **START** your Bitcoin Core service. You should see it begin at 99%+ pre-synced.
#. Switch back to `https://example-bbb.local`, selecting **Services > Bitcoin Core**, **CONFIGURE**, configure it as desired, **SAVE** and then **START** your Bitcoin Core service. You should see it begin at 99%+ pre-synced.
#. You can now restart your Bitcoin Core service on `https://example-A.local` (**Services > Bitcoin Core > Start**)
#. You can now restart your Bitcoin Core service on `https://example-aaa.local` via **Services > Bitcoin Core > Start**.
.. _bitcoin-service: