msgid "Closing OnionShare tabs you host destroys them, preventing reuse. Persistently hosted websites are available on the same address even if the computer they are shared from is rebooted."
msgid "When opening OnionShare, your saved tabs from the prior session will start opened. Each service then can be started manually, and will be available on the same OnionShare address and be protected by the same private key."
msgid "The Tor Browser will ask you to enter your private key when you load an OnionShare service. If you want to allow the public to use your service, it's better to disable the private key altogether."
msgid "To turn off the private key for any tab, check the \"This is a public OnionShare service (disables private key)\" box before starting the server. Then the server will be public and a private key is not needed to load it in the Tor Browser."
msgid "When people load OnionShare services in the Tor Browser they see the default title for each type of service. For example, the default title for chat services is \"OnionShare Chat\"."
msgid "OnionShare supports scheduling exactly when a service should start and stop. Before starting a server, click \"Show advanced settings\" in its tab and then check the boxes next to either \"Start onion service at scheduled time\", \"Stop onion service at scheduled time\", or both, and set the respective desired dates and times."
msgid "Services scheduled to start in the future display a countdown timer when the \"Start sharing\" button is clicked. Services scheduled to stop in the future display a countdown timer when started."
msgid "**Scheduling an OnionShare service to automatically start can be used as a dead man's switch**. This means your service is made public at a given time in the future if you are not there to prevent it. If nothing happens to you, you can cancel the service before it's scheduled to start."
msgid "**Scheduling an OnionShare service to automatically stop limits its exposure**. If you want to share secret info or something that will be outdated, you can do so for selected limited time."
msgid "Info about installing it on different operating systems can be found in the `CLI README file <https://github.com/onionshare/onionshare/blob/develop/cli/README.md>`_ in the Git repository."
msgid "It is possible to automatically start OnionShare from the CLI using a systemd unit file."
msgstr ""
#: ../../source/advanced.rst:174
msgid "You may find this particularly useful if you are operating in 'persistent' mode, and want to start the same onion service every time your machine starts."
msgstr ""
#: ../../source/advanced.rst:176
msgid "To do this, you need to prepare some OnionShare json config first."
msgstr ""
#: ../../source/advanced.rst:178
msgid "Here is the main OnionShare config. In this example, it's stored in ``/home/user/.config/onionshare/onionshare.json``. You may need to adjust some of the settings, but if you already have OnionShare installed, it probably looks much like this already::"
msgstr ""
#: ../../source/advanced.rst:207
msgid "Notice the 'persistent_tabs' section. We will now create a file at ``/home/user/.config/onionshare/persistent/my-persistent-onion.json``, that looks like this::"
msgstr ""
#: ../../source/advanced.rst:247
msgid "**Don't actually use this private key, service_id or client_auth keys! They are shown only as an example. Never share the private_key with anyone.**"
msgstr ""
#: ../../source/advanced.rst:249
msgid "The easiest way to generate the onion address and private key is to first create a 'pinned' OnionShare tab in the desktop app and started the share for the first time. This will then have saved the persistent settings to your ``.config/onionshare/persistent/`` folder with a random name. You can unpin that tab once you've generated it the first time. Or, you can leave it where it is, and use that persistent file in your systemd unit file below."
msgstr ""
#: ../../source/advanced.rst:251
msgid "Now you can create a systemd unit file in ``/etc/systemd/system/onionshare-cli.service``. Be sure to adjust the User and Group to your own user/group, as well as changes to any paths to the onionshare-cli binary or the paths to your JSON configs and shares."
msgstr ""
#: ../../source/advanced.rst:253
msgid "The systemd unit file should look like this::"
msgstr ""
#: ../../source/advanced.rst:268
msgid "Note that although ``/home/user/my-shared-file.txt`` was defined in the ``filenames`` section of the ``my-persistent-onion.json`` file, it's still necessary to specify it as the argument to the onionshare-cli command."
msgstr ""
#: ../../source/advanced.rst:270
msgid "Be sure to run ``sudo systemctl daemon-reload`` after creating the unit file."
msgstr ""
#: ../../source/advanced.rst:272
msgid "Now you can run ``sudo systemctl start onionshare-cli.service``. If you have ``journalctl`` installed, you can run ``sudo journalctl -f -t onionshare-cli``, and you should see some output of your service starting::"
msgstr ""
#: ../../source/advanced.rst:282
msgid "If you don't want your users to use a Private Key, set ``public`` to be ``true`` in the ``general`` settings of the my-persistent-onion.json file."
msgid "You may want to migrate your OnionShare data when switching to another computer. This is especially true if you had a 'persistent' onion address and you want to preserve it."
