aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorng0 <ng0@infotropique.org>2017-10-30 23:42:12 +0000
committerng0 <ng0@infotropique.org>2017-10-30 23:42:12 +0000
commit68705e67c4883dcbec31d45b0086d65f981327d2 (patch)
tree0182c782f6ef528bd58386f1a89911002feaa62c /doc
parentc26ba4980aab5bf9f41cd69b6819e5bfb70f79be (diff)
downloadgnunet-68705e67c4883dcbec31d45b0086d65f981327d2.tar.gz
gnunet-68705e67c4883dcbec31d45b0086d65f981327d2.zip
batch
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation/chapters/developer.texi2
-rw-r--r--doc/documentation/chapters/installation.texi227
2 files changed, 104 insertions, 125 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi
index df187f39b..a2032f479 100644
--- a/doc/documentation/chapters/developer.texi
+++ b/doc/documentation/chapters/developer.texi
@@ -11,7 +11,7 @@ For developers, GNUnet is:
11@itemize @bullet 11@itemize @bullet
12@item developed by a community that believes in the GNU philosophy 12@item developed by a community that believes in the GNU philosophy
13@item Free Software (Free as in Freedom), licensed under the 13@item Free Software (Free as in Freedom), licensed under the
14@xref{GNU General Public License} 14GNU General Public License
15@item A set of standards, including coding conventions and 15@item A set of standards, including coding conventions and
16architectural rules 16architectural rules
17@item A set of layered protocols, both specifying the communication 17@item A set of layered protocols, both specifying the communication
diff --git a/doc/documentation/chapters/installation.texi b/doc/documentation/chapters/installation.texi
index 38eb7c0b0..7be1e9833 100644
--- a/doc/documentation/chapters/installation.texi
+++ b/doc/documentation/chapters/installation.texi
@@ -452,61 +452,23 @@ $ sudo apt-get install automake autopoint autoconf libtool
452@node Install libgcrypt 1.6 and libgpg-error 452@node Install libgcrypt 1.6 and libgpg-error
453@subsection Install libgcrypt 1.6 and libgpg-error 453@subsection Install libgcrypt 1.6 and libgpg-error
454 454
455@example 455@ref{generic source installation - libgpg-error}
456$ wget ftp://ftp.gnupg.org/gcrypt/libgpg-error/libgpg-error-1.12.tar.bz2
457$ tar xf libgpg-error-1.12.tar.bz2
458$ cd libgpg-error-1.12
459$ ./configure
460$ sudo make install ; cd ..
461@end example
462 456
463@node Install gnutls with DANE support 457@node Install gnutls with DANE support
464@subsection Install gnutls with DANE support 458@subsection Install gnutls with DANE support
465 459
466@example 460@itemize @bullet
467$ wget http://www.lysator.liu.se/~nisse/archive/nettle-2.7.1.tar.gz 461@item @ref{generic source installation - nettle}
468$ tar xf nettle-2.7.1.tar.gz 462@item @ref{generic source installation - ldns}
469$ cd nettle-2.7.1 463@item @ref{generic source installation - libunbound/unbound}
470$ ./configure 464@item @ref{generic source installation - gnutls}
471$ sudo make install ; cd .. 465@item @ref{generic source installation - libgcrypt}
472@end example 466@end itemize
473
474@example
475$ wget https://www.nlnetlabs.nl/downloads/ldns/ldns-1.6.16.tar.gz
476$ tar xf ldns-1.6.16.tar.gz
477$ cd ldns-1.6.16
478$ ./configure
479$ sudo make install ; cd ..
480@end example
481
482@example
483$ wget https://unbound.net/downloads/unbound-1.4.21.tar.gz
484$ tar xf unbound-1.4.21.tar.gz
485$ cd unbound-1.4.21
486$ ./configure
487$ sudo make install ; cd ..
488@end example
489
490@example
491$ wget ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.17.tar.xz
492$ tar xf gnutls-3.1.17.tar.xz
493$ cd gnutls-3.1.17
494$ ./configure
495$ sudo make install ; cd ..
496@end example
497
498@example
499$ wget ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.6.0.tar.bz2
500$ tar xf libgcrypt-1.6.0.tar.bz2
501$ cd libgcrypt-1.6.0
502$ ./configure
503$ sudo make install ; cd ..
504@end example
505 467
506@node Install libgnurl 468@node Install libgnurl
507@subsection Install libgnurl 469@subsection Install libgnurl
508 470
509Follow @ref{generic source installation - libgnurl}. 471Follow the @ref{generic source installation - libgnurl}.
510 472
511@node Install libmicrohttpd from Git 473@node Install libmicrohttpd from Git
512@subsection Install libmicrohttpd from Git 474@subsection Install libmicrohttpd from Git
@@ -1559,20 +1521,7 @@ $ cd ..
1559 1521
1560Install libgnurl: 1522Install libgnurl:
1561 1523
1562@example 1524@pxref{generic source installation - libgnurl}.
1563$ wget https://gnunet.org/sites/default/files/gnurl-7.35.0.tar.bz2
1564$ tar xf gnurl-7.35.0.tar.bz2
1565$ cd gnurl-7.35.0
1566$ ./configure --enable-ipv6 --with-gnutls --without-libssh2 \
1567--without-libmetalink --without-winidn --without-librtmp
1568--without-nghttp2 --without-nss --without-cyassl --without-polarssl \
1569--without-ssl --without-winssl --without-darwinssl --disable-sspi \
1570--disable-ntlm-wb --disable-ldap --disable-rtsp --disable-dict \
1571--disable-telnet --disable-tftp --disable-pop3 --disable-imap \
1572--disable-smtp --disable-gopher --disable-file --disable-ftp
1573$ sudo make install@
1574$ cd ..@
1575@end example
1576 1525
1577Install GNUnet: 1526Install GNUnet:
1578 1527
@@ -2241,7 +2190,6 @@ file by hand, this is not recommended for anyone except for developers
2241as it requires a more in-depth understanding of the configuration files 2190as it requires a more in-depth understanding of the configuration files
2242and internal dependencies of GNUnet. 2191and internal dependencies of GNUnet.
2243 2192
2244
2245@node Configuring the Friend-to-Friend (F2F) mode 2193@node Configuring the Friend-to-Friend (F2F) mode
2246@subsection Configuring the Friend-to-Friend (F2F) mode 2194@subsection Configuring the Friend-to-Friend (F2F) mode
2247 2195
@@ -2271,18 +2219,18 @@ The resulting output of this command needs to be added to your
2271per friend with the output from the above command. 2219per friend with the output from the above command.
2272 2220
2273You then specify the location of your @file{friends} file in the 2221You then specify the location of your @file{friends} file in the
2274"FRIENDS" option of the "topology" section. 2222@code{FRIENDS} option of the "topology" section.
2275 2223
2276Once you have created the @file{friends} file, you can tell GNUnet to only 2224Once you have created the @file{friends} file, you can tell GNUnet to only
2277connect to your friends by setting the "FRIENDS-ONLY" option (again in 2225connect to your friends by setting the @code{FRIENDS-ONLY} option
2278the "topology" section) to YES. 2226(again in the "topology" section) to YES.
2279 2227
2280If you want to run in mixed-mode, set "FRIENDS-ONLY" to NO and configure a 2228If you want to run in mixed-mode, set "FRIENDS-ONLY" to NO and configure a
2281minimum number of friends to have (before connecting to arbitrary peers) 2229minimum number of friends to have (before connecting to arbitrary peers)
2282under the "MINIMUM-FRIENDS" option. 2230under the "MINIMUM-FRIENDS" option.
2283 2231
2284If you want to operate in normal P2P-only mode, simply set 2232If you want to operate in normal P2P-only mode, simply set
2285"MINIMUM-FRIENDS" to zero and "FRIENDS_ONLY" to NO. 2233@code{MINIMUM-FRIENDS} to zero and @code{FRIENDS_ONLY} to NO.
2286This is the default. 2234This is the default.
2287 2235
2288@node Configuring the hostlist to bootstrap 2236@node Configuring the hostlist to bootstrap
@@ -2301,7 +2249,7 @@ To use these bootstrap servers you have to configure the hostlist daemon
2301to activate bootstrapping. 2249to activate bootstrapping.
2302 2250
2303To activate bootstrapping, edit the @code{[hostlist]}-section in your 2251To activate bootstrapping, edit the @code{[hostlist]}-section in your
2304configuration file. You have to set the argument "-b" in the 2252configuration file. You have to set the argument @command{-b} in the
2305options line: 2253options line:
2306 2254
2307@example 2255@example
@@ -2337,8 +2285,8 @@ messages, your peer can download these lists and connect to the peers
2337included. These lists are persistent, which means that they are saved to 2285included. These lists are persistent, which means that they are saved to
2338your hard disk regularly and are loaded during startup. 2286your hard disk regularly and are loaded during startup.
2339 2287
2340To activate hostlist learning you have to add the "-e" switch to the 2288To activate hostlist learning you have to add the @command{-e}
2341OPTIONS line in the hostlist section: 2289switch to the @code{OPTIONS} line in the hostlist section:
2342 2290
2343@example 2291@example
2344[hostlist] 2292[hostlist]
@@ -2347,7 +2295,7 @@ OPTIONS = -b -e
2347 2295
2348@noindent 2296@noindent
2349Furthermore you can specify in which file the lists are saved. 2297Furthermore you can specify in which file the lists are saved.
2350To save the lists in the file "hostlists.file" just add the line: 2298To save the lists in the file @file{hostlists.file} just add the line:
2351 2299
2352@example 2300@example
2353HOSTLISTFILE = hostlists.file 2301HOSTLISTFILE = hostlists.file
@@ -2371,7 +2319,7 @@ HOSTLISTFILE = $SERVICEHOME/hostlists.file
2371The hostlist client can be configured to use a proxy to connect to the 2319The hostlist client can be configured to use a proxy to connect to the
2372hostlist server. 2320hostlist server.
2373This functionality can be configured in the configuration file directly 2321This functionality can be configured in the configuration file directly
2374or using the gnunet-setup tool. 2322or using the @command{gnunet-setup} tool.
2375 2323
2376The hostlist client supports the following proxy types at the moment: 2324The hostlist client supports the following proxy types at the moment:
2377 2325
@@ -2418,17 +2366,18 @@ If you operate a peer permanently connected to GNUnet you can configure
2418your peer to act as a hostlist server, providing other peers the list of 2366your peer to act as a hostlist server, providing other peers the list of
2419peers known to him. 2367peers known to him.
2420 2368
2421Yor server can act as a bootstrap server and peers needing to obtain a 2369Your server can act as a bootstrap server and peers needing to obtain a
2422list of peers can contact it to download this list. 2370list of peers can contact it to download this list.
2423To download this hostlist the peer uses HTTP. 2371To download this hostlist the peer uses HTTP.
2424For this reason you have to build your peer with libcurl and microhttpd 2372For this reason you have to build your peer with libgnurl (or libcurl)
2425support. How you build your peer with this options can be found here: 2373and microhttpd support.
2426@uref{https://gnunet.org/generic_installation} 2374How you build your peer with these options can be found here:
2375@xref{Generic installation instructions}.
2427 2376
2428To configure your peer to act as a bootstrap server you have to add the 2377To configure your peer to act as a bootstrap server you have to add the
2429@code{-p} option to OPTIONS in the @code{[hostlist]} section of your 2378@command{-p} option to @code{OPTIONS} in the @code{[hostlist]} section
2430configuration file. Besides that you have to specify a port number for 2379of your configuration file.
2431the http server. 2380Besides that you have to specify a port number for the http server.
2432In conclusion you have to add the following lines: 2381In conclusion you have to add the following lines:
2433 2382
2434@example 2383@example
@@ -2465,7 +2414,7 @@ The URL used to download the list will be
2465Please notice: 2414Please notice:
2466 2415
2467@itemize @bullet 2416@itemize @bullet
2468@item The hostlist is not human readable, so you should not try to 2417@item The hostlist is @b{not} human readable, so you should not try to
2469download it using your webbrowser. Just point your GNUnet peer to the 2418download it using your webbrowser. Just point your GNUnet peer to the
2470address! 2419address!
2471@item Advertising without providing a hostlist does not make sense and 2420@item Advertising without providing a hostlist does not make sense and
@@ -2475,13 +2424,13 @@ will not work.
2475@node Configuring the datastore 2424@node Configuring the datastore
2476@subsection Configuring the datastore 2425@subsection Configuring the datastore
2477 2426
2478The datastore is what GNUnet uses to for long-term storage of file-sharing 2427The datastore is what GNUnet uses for long-term storage of file-sharing
2479data. Note that long-term does not mean 'forever' since content does have 2428data. Note that long-term does not mean 'forever' since content does have
2480an expiration date, and of course storage space is finite (and hence 2429an expiration date, and of course storage space is finite (and hence
2481sometimes content may have to be discarded). 2430sometimes content may have to be discarded).
2482 2431
2483Use the "QUOTA" option to specify how many bytes of storage space you are 2432Use the @code{QUOTA} option to specify how many bytes of storage space
2484willing to dedicate to GNUnet. 2433you are willing to dedicate to GNUnet.
2485 2434
2486In addition to specifying the maximum space GNUnet is allowed to use for 2435In addition to specifying the maximum space GNUnet is allowed to use for
2487the datastore, you need to specify which database GNUnet should use to do 2436the datastore, you need to specify which database GNUnet should use to do
@@ -2523,8 +2472,8 @@ inconsistencies. Some of the other databases do not support repair.
2523 2472
2524@itemize @bullet 2473@itemize @bullet
2525 2474
2526@item In @code{gnunet.conf} set in section "DATASTORE" the value for 2475@item In @file{gnunet.conf} set in section @code{DATASTORE} the value for
2527"DATABASE" to "mysql". 2476@code{DATABASE} to @code{mysql}.
2528 2477
2529@item Access mysql as root: 2478@item Access mysql as root:
2530 2479
@@ -2534,7 +2483,7 @@ $ mysql -u root -p
2534 2483
2535@noindent 2484@noindent
2536and issue the following commands, replacing $USER with the username 2485and issue the following commands, replacing $USER with the username
2537that will be running gnunet-arm (so typically "gnunet"): 2486that will be running @command{gnunet-arm} (so typically "gnunet"):
2538 2487
2539@example 2488@example
2540CREATE DATABASE gnunet; 2489CREATE DATABASE gnunet;
@@ -2574,15 +2523,30 @@ mysql> use gnunet;
2574@end example 2523@end example
2575 2524
2576@noindent 2525@noindent
2577If you get the message "Database changed" it probably works. 2526If you get the message
2578 2527
2579If you get "ERROR 2002: Can't connect to local MySQL server@ 2528@example
2580through socket '/tmp/mysql.sock' (2)" it may be resolvable by 2529Database changed
2530@end example
2531
2532@noindent
2533it probably works.
2534
2535If you get
2536
2537@example
2538ERROR 2002: Can't connect to local MySQL server
2539through socket '/tmp/mysql.sock' (2)
2540@end example
2541
2542@noindent
2543it may be resolvable by
2581 2544
2582@example 2545@example
2583ln -s /var/run/mysqld/mysqld.sock /tmp/mysql.sock 2546ln -s /var/run/mysqld/mysqld.sock /tmp/mysql.sock
2584@end example 2547@end example
2585 2548
2549@noindent
2586so there may be some additional trouble depending on your mysql setup. 2550so there may be some additional trouble depending on your mysql setup.
2587 2551
2588@node Performance Tuning 2552@node Performance Tuning
@@ -2607,7 +2571,7 @@ the only application on your system using MySQL.
2607 2571
2608If you want to run the testcases, you must create a second database 2572If you want to run the testcases, you must create a second database
2609"gnunetcheck" with the same username and password. This database will 2573"gnunetcheck" with the same username and password. This database will
2610then be used for testing ("make check"). 2574then be used for testing (@command{make check}).
2611 2575
2612@node Configuring the Postgres database 2576@node Configuring the Postgres database
2613@subsection Configuring the Postgres database 2577@subsection Configuring the Postgres database
@@ -2637,9 +2601,9 @@ earlier versions as well.
2637@subsection Manual setup instructions 2601@subsection Manual setup instructions
2638 2602
2639@itemize @bullet 2603@itemize @bullet
2640@item In @code{gnunet.conf} set in section "DATASTORE" the value for 2604@item In @file{gnunet.conf} set in section @code{DATASTORE} the value for
2641"DATABASE" to "postgres". 2605@code{DATABASE} to @code{postgres}.
2642@item Access Postgres to create a user:@ 2606@item Access Postgres to create a user:
2643 2607
2644@table @asis 2608@table @asis
2645@item with Postgres 8.x, use: 2609@item with Postgres 8.x, use:
@@ -2652,7 +2616,7 @@ $ createuser
2652@noindent 2616@noindent
2653and enter the name of the user running GNUnet for the role interactively. 2617and enter the name of the user running GNUnet for the role interactively.
2654Then, when prompted, do not set it to superuser, allow the creation of 2618Then, when prompted, do not set it to superuser, allow the creation of
2655databases, and do not allow the creation of new roles.@ 2619databases, and do not allow the creation of new roles.
2656 2620
2657@item with Postgres 9.x, use: 2621@item with Postgres 9.x, use:
2658 2622
@@ -2662,7 +2626,7 @@ $ createuser -d $GNUNET_USER
2662@end example 2626@end example
2663 2627
2664@noindent 2628@noindent
2665where $GNUNET_USER is the name of the user running GNUnet.@ 2629where $GNUNET_USER is the name of the user running GNUnet.
2666 2630
2667@end table 2631@end table
2668 2632
@@ -2704,7 +2668,7 @@ expected to be wiped completely each time GNUnet is restarted (or the
2704system is rebooted). 2668system is rebooted).
2705 2669
2706You need to specify how many bytes GNUnet is allowed to use for the 2670You need to specify how many bytes GNUnet is allowed to use for the
2707datacache using the "QUOTA" option in the section "dhtcache". 2671datacache using the @code{QUOTA} option in the section @code{[dhtcache]}.
2708Furthermore, you need to specify which database backend should be used to 2672Furthermore, you need to specify which database backend should be used to
2709store the data. Currently, you have the choice between 2673store the data. Currently, you have the choice between
2710sqLite, MySQL and Postgres. 2674sqLite, MySQL and Postgres.
@@ -2714,8 +2678,8 @@ sqLite, MySQL and Postgres.
2714 2678
2715In order to use GNUnet for file-sharing, you first need to make sure 2679In order to use GNUnet for file-sharing, you first need to make sure
2716that the file-sharing service is loaded. 2680that the file-sharing service is loaded.
2717This is done by setting the AUTOSTART option in section "fs" to "YES". 2681This is done by setting the @code{AUTOSTART} option in
2718Alternatively, you can run 2682section @code{[fs]} to "YES". Alternatively, you can run
2719 2683
2720@example 2684@example
2721$ gnunet-arm -i fs 2685$ gnunet-arm -i fs
@@ -2763,26 +2727,29 @@ The @code{-l} option is used to specify the log file.
2763 2727
2764Since most GNUnet services are managed by @code{gnunet-arm}, using the 2728Since most GNUnet services are managed by @code{gnunet-arm}, using the
2765@code{-l} or @code{-L} options directly is not possible. 2729@code{-l} or @code{-L} options directly is not possible.
2766Instead, they can be specified using the "OPTIONS" configuration value in 2730Instead, they can be specified using the @code{OPTIONS} configuration
2767the respective section for the respective service. 2731value in the respective section for the respective service.
2768In order to enable logging globally without editing the "OPTIONS" values 2732In order to enable logging globally without editing the @code{OPTIONS}
2769for each service, @code{gnunet-arm} supports a "GLOBAL_POSTFIX" option. 2733values for each service, @command{gnunet-arm} supports a
2734@code{GLOBAL_POSTFIX} option.
2770The value specified here is given as an extra option to all services for 2735The value specified here is given as an extra option to all services for
2771which the configuration does contain a service-specific "OPTIONS" field. 2736which the configuration does contain a service-specific @code{OPTIONS}
2737field.
2772 2738
2773"GLOBAL_POSTFIX" can contain the special sequence "@{@}" which is replaced 2739@code{GLOBAL_POSTFIX} can contain the special sequence "@{@}" which
2774by the name of the service that is being started. Furthermore, 2740is replaced by the name of the service that is being started.
2775@code{GLOBAL_POSTFIX} is special in that sequences starting with "$" 2741Furthermore, @code{GLOBAL_POSTFIX} is special in that sequences
2776anywhere in the string are expanded (according to options in "PATHS"); 2742starting with "$" anywhere in the string are expanded (according
2777this expansion otherwise is only happening for filenames and then the "$" 2743to options in @code{PATHS}); this expansion otherwise is
2778must be the first character in the option. Both of these restrictions do 2744only happening for filenames and then the "$" must be the
2779not apply to "GLOBAL_POSTFIX". 2745first character in the option. Both of these restrictions do
2780Note that specifying @code{%} anywhere in the "GLOBAL_POSTFIX" disables 2746not apply to @code{GLOBAL_POSTFIX}.
2781both of these features. 2747Note that specifying @code{%} anywhere in the @code{GLOBAL_POSTFIX}
2748disables both of these features.
2782 2749
2783In summary, in order to get all services to log at level "INFO" to 2750In summary, in order to get all services to log at level
2784log-files called @code{SERVICENAME-logs}, the following global prefix 2751@code{INFO} to log-files called @code{SERVICENAME-logs}, the
2785should be used: 2752following global prefix should be used:
2786 2753
2787@example 2754@example
2788GLOBAL_POSTFIX = -l $SERVICEHOME/@{@}-logs -L INFO 2755GLOBAL_POSTFIX = -l $SERVICEHOME/@{@}-logs -L INFO
@@ -3008,9 +2975,11 @@ The interface channel depends on the wlan network that the card is
3008connected to. If no connection has been made since the start of the 2975connected to. If no connection has been made since the start of the
3009computer, it is usually the first channel of the card. 2976computer, it is usually the first channel of the card.
3010Peers will only find each other and communicate if they are on the same 2977Peers will only find each other and communicate if they are on the same
3011channel. Channels must be set manually (i.e. using 2978channel. Channels must be set manually, i.e. using:
3012@code{iwconfig wlan0 channel 1}).
3013 2979
2980@example
2981iwconfig wlan0 channel 1
2982@end example
3014 2983
3015@node Configuring HTTP(S) reverse proxy functionality using Apache or nginx 2984@node Configuring HTTP(S) reverse proxy functionality using Apache or nginx
3016@subsection Configuring HTTP(S) reverse proxy functionality using Apache or nginx 2985@subsection Configuring HTTP(S) reverse proxy functionality using Apache or nginx
@@ -3048,7 +3017,16 @@ As an example we want to use GNUnet peer running:
3048And we want the webserver to accept GNUnet traffic under 3017And we want the webserver to accept GNUnet traffic under
3049@code{http://www.foo.org/bar/}. The required steps are described here: 3018@code{http://www.foo.org/bar/}. The required steps are described here:
3050 3019
3051@strong{Configure your Apache2 HTTP webserver} 3020@menu
3021* Reverse Proxy - Configure your Apache2 HTTP webserver::
3022* Reverse Proxy - Configure your Apache2 HTTPS webserver::
3023* Reverse Proxy - Configure your nginx HTTPS webserver::
3024* Reverse Proxy - Configure your nginx HTTP webserver::
3025* Reverse Proxy - Configure your GNUnet peer::
3026@end menu
3027
3028@node Reverse Proxy - Configure your Apache2 HTTP webserver
3029@subsubsection Reverse Proxy - Configure your Apache2 HTTP webserver
3052 3030
3053First of all you need mod_proxy installed. 3031First of all you need mod_proxy installed.
3054 3032
@@ -3067,8 +3045,8 @@ ProxyPassReverse http://gnunet.foo.org:1080/
3067</Location> 3045</Location>
3068@end example 3046@end example
3069 3047
3070@noindent 3048@node Reverse Proxy - Configure your Apache2 HTTPS webserver
3071@strong{Configure your Apache2 HTTPS webserver} 3049@subsubsection Reverse Proxy - Configure your Apache2 HTTPS webserver
3072 3050
3073We assume that you already have an HTTPS server running, if not please 3051We assume that you already have an HTTPS server running, if not please
3074check how to configure a HTTPS host. An easy to use example is the 3052check how to configure a HTTPS host. An easy to use example is the
@@ -3092,7 +3070,8 @@ More information about the apache mod_proxy configuration can be found
3092here: @uref{http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass} 3070here: @uref{http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass}
3093. 3071.
3094 3072
3095@strong{Configure your nginx HTTPS webserver} 3073@node Reverse Proxy - Configure your nginx HTTPS webserver
3074@subsubsection Reverse Proxy - Configure your nginx HTTPS webserver
3096 3075
3097Since nginx does not support chunked encoding, you first of all have to 3076Since nginx does not support chunked encoding, you first of all have to
3098install @code{chunkin}: @uref{http://wiki.nginx.org/HttpChunkinModule}. 3077install @code{chunkin}: @uref{http://wiki.nginx.org/HttpChunkinModule}.
@@ -3125,8 +3104,8 @@ proxy_next_upstream error timeout invalid_header http_500 http_503 http_502 http
3125@} 3104@}
3126@end example 3105@end example
3127 3106
3128@noindent 3107@node Reverse Proxy - Configure your nginx HTTP webserver
3129@strong{Configure your nginx HTTPS webserver} 3108@subsubsection Reverse Proxy - Configure your nginx HTTP webserver
3130 3109
3131Edit your webserver configuration. Edit @file{/etc/nginx/nginx.conf} or 3110Edit your webserver configuration. Edit @file{/etc/nginx/nginx.conf} or
3132the site-specific configuration file. 3111the site-specific configuration file.
@@ -3146,8 +3125,8 @@ proxy_next_upstream error timeout invalid_header http_500 http_503 http_502 http
3146@} 3125@}
3147@end example 3126@end example
3148 3127
3149@noindent 3128@node Reverse Proxy - Configure your GNUnet peer
3150@strong{Configure your GNUnet peer} 3129@subsubsection Reverse Proxy - Configure your GNUnet peer
3151 3130
3152To have your GNUnet peer announce the address, you have to specify the 3131To have your GNUnet peer announce the address, you have to specify the
3153@code{EXTERNAL_HOSTNAME} option in the @code{[transport-http_server]} 3132@code{EXTERNAL_HOSTNAME} option in the @code{[transport-http_server]}