free
/
freedomboneeee
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document running the client command

This commit is contained in:
Bob Mottram 2016-11-23 17:36:09 +00:00
parent adcc8878a4
commit 90b82e5ed4
2 changed files with 24 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/EN/homeserver.org
View File

@ -17,14 +17,14 @@
The quickest way to get started is as follows. You will need to be running a Debian based system (version 8 or later), have an old but still working laptop or netbook which you can use as a server, and 8GB or larger USB thumb drive and an ethernet cable to connect the laptop to your internet router.
First you will need to create an image. On a debian based distro:
First install freedombone onto your local system (not the target hardware that you want to run Freedombone on). On a debian based distro:
#+begin_src bash
sudo apt-get install git
git clone https://github.com/bashrc/freedombone
cd freedombone
git checkout stockholm
make install
sudo make install
freedombone-image --setup debian
freedombone-image -t i386 --onion yes
#+end_src
@ -36,14 +36,21 @@ sudo pacman -S git
git clone https://github.com/bashrc/freedombone
cd freedombone
git checkout stockholm
make install
sudo make install
freedombone-image --setup parabola
freedombone-image -t i386 --onion yes
#+end_src
Now prepare your local system to talk to the freedombone by running. This will set up avahi and create ssh keys if necessary.
#+begin_src bash
freedombone-client
#+end_src
#+BEGIN_CENTER
[[file:images/tor_onion.jpg]]
#+END_CENTER
The version in which sites are available only via onion addresses is the easiest to get started with, since you can evaluate the system without committing to buying an ICANN domain name or needing to get involved with SSL/TLS certificates at all. However, if you do want your sites to be available typically as subdomains of a domain name which you own then remove the *--onion yes* option from the last command shown above.
If you want to create images for microSD cards used within various single board computers then replace the *i386* with *beaglebone* / *cubieboard2* / *cubietruck* / *a20-olinuxino-lime* / *a20-olinuxino-lime2* / *a20-olinuxino-micro* or *apu*.

18
website/EN/homeserver.html
View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2016-11-11 Fri 21:30 -->
<!-- 2016-11-23 Wed 17:35 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
@ -251,7 +251,7 @@ The quickest way to get started is as follows. You will need to be running a Deb
</p>
<p>
First you will need to create an image. On a debian based distro:
First install freedombone onto your local system (not the target hardware that you want to run Freedombone on). On a debian based distro:
</p>
<div class="org-src-container">
@ -259,7 +259,7 @@ First you will need to create an image. On a debian based distro:
git clone https://github.com/bashrc/freedombone
<span class="org-builtin">cd</span> freedombone
git checkout stockholm
make install
sudo make install
freedombone-image --setup debian
freedombone-image -t i386 --onion yes
</pre>
@ -274,12 +274,21 @@ Or on Arch/Parabola:
git clone https://github.com/bashrc/freedombone
<span class="org-builtin">cd</span> freedombone
git checkout stockholm
make install
sudo make install
freedombone-image --setup parabola
freedombone-image -t i386 --onion yes
</pre>
</div>
<p>
Now prepare your local system to talk to the freedombone by running. This will set up avahi and create ssh keys if necessary.
</p>
<div class="org-src-container">
<pre class="src src-bash">freedombone-client
</pre>
</div>
<div class="org-center">
<div class="figure">
@ -287,6 +296,7 @@ freedombone-image -t i386 --onion yes
</p>
</div>
</div>
<p>
The version in which sites are available only via onion addresses is the easiest to get started with, since you can evaluate the system without committing to buying an ICANN domain name or needing to get involved with SSL/TLS certificates at all. However, if you do want your sites to be available typically as subdomains of a domain name which you own then remove the <b>&#x2013;onion yes</b> option from the last command shown above.
</p>