Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- dapnetnodeinstall [2018/02/26 22:12]
dh3wr
+++ dapnetnodeinstall [2018/10/23 09:22] (aktuell)
df2et [Installation DAPNET-Core]
@@ Zeile 1: / Zeile 1: @@
 ====== Installation procedure for new DAPNET node ======
+<color #ed1c24>
+ATTENTION: Due to serious problems of the current version of DAPNET-CORE we do not accept any new cores. A new version overcoming this issues is in progress. If you want to run your own core, please wait for the new version being released!</color>
 ===== Introduction =====
@@ Zeile 38: / Zeile 40: @@
 <code>sudo mkdir /opt/dapnet</code>
-Make dapnet the owner of this directory
+Make ''dapnet'' the owner of this directory
 <code>sudo chown dapnet /opt/dapnet</code>
-Change to user //dapnet//. If you don't have a user ''dapnet'' on your system, make one. If you don't know how, ask google.
+Change to user ''dapnet''. If you don't have a user ''dapnet'' on your system, make one. If you don't know how, ask google.
 <code>sudo su dapnet</code>
@@ Zeile 85: / Zeile 87: @@
 </code>
-Contact us or one of the existing Core sysops and get the password. We assume hier it is "geheim". So put the real one in the line:
+If you want the Core to bind to a specific address you can extend the TCP config
+<code><TCP bind_port="7800" bind_addr="127.0.0.1" /></code>
+{{:icons:warning.png |}}**Contact us or one of the existing Core sysops to have your node added and get the password**.{{ :icons:warning.png|}}
+We assume here the password is "geheim". So put the real one in the line:
 <code>auth_value="geheim"/></code>
-At the bottom, put the callsign of the core in lowercase. The example here ist db0abc
+At the bottom, put the callsign of the core in lowercase. The example here ist ''db0abc''. Enter the one that is registered in the DAPNET. Use lowercase letters.
 <code><pbcast.GMS name="db0abc@DAPNET"</code>
@@ Zeile 96: / Zeile 104: @@
 ==== Alternative 1 to run the Node ====
-Change to <code>cd /opt/dapnet/Core/local</code> and start at screen, so the program keeps running even if your SSH connection is closed
+Change to <code>cd /opt/dapnet/Core/local</code> and start a ''screen'', so the program keeps running even if your SSH connection is closed. Install ''screen'' if not already installed.
+<code>sudo apt-get install screen</code>
+Run the ''screen''
-<code>sudo apt-get install screen</code> (if not already installed)
 <code>screen</code>
@@ Zeile 123: / Zeile 134: @@
 The source code is already downloaded to <code>/opt/dapnet/Web</code>. Now install the apache2 webserver and the php module if not already present.
-<code>apt-get install apache2 libapache2-mod-php5</code>
+<code>apt-get install apache2</code>
 Edit <code>/etc/apache2/sites-available/000-default.conf</code> and change
-<code>DocumentRoot /opt/dapnet/Web/dist</code>
+<code>DocumentRoot dist</code>
 Insert below this line:
@@ Zeile 143: / Zeile 154: @@
 Change to <code>cd /opt/dapnet/Web</code> and follow the instructions on [[https://github.com/DecentralizedAmateurPagingNetwork/Web|Github]].
-Now the web interface is accessable on http://YOURURL .
+Now the web interface is accessable on ''http://YOURURL'' .
+==== Hint to run the REST-API on the same HTTP Port ====
+Normally, the REST-API runs on port 8080. If you just have port 80 open for your website and don't want to add port 8080, you can use the Apache webserver as a proxy to process the API requests.
+Add to your apache config:
+<file>
+        ProxyPass "/api" "http://URLOFYOURCORE:8080
+        ProxyPassReverse "/api" "http://URLOFYOURCORE:8080"
+</file>
+In the settings of the DAPNET-WEG, enter in ''/src/store/defaultUrls.json'' the API URL to
+<code>
+    "api": "http://YOURWEBSITEURL/api",
+</code>
+Restart the apache and build the website again:
+<code>
+sudo systemctl restart apache2
+cd /opt/dapnet/Web/
+npm run build
+</code>
 ===== First Steps =====
 Ask us for your personal login data and happy paging.

DAPNET DokuWiki

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Unterschiede

Seiten-Werkzeuge