Rozdíly

Zde můžete vidět rozdíly mezi vybranou verzí a aktuální verzí dané stránky.

--- en_installation:installation_guide [2023/01/20 15:12] – kozak
+++ en_installation:installation_guide [2025/01/10 14:00] (aktuální) – [Installation guide:] kozak
@@ Řádek 10: / Řádek 10: @@
   - **Re-log as a new user (directly on server console or remote via ssh)**
       * With default ssh port 22:
-        * "ssh youruser@yourIP" or "ssh youruser@blockchain.yourDomain"
+        * ''ssh youruser@yourIP" or "ssh youruser@blockchain.yourDomain''
       * Different port:
-        * "ssh youruser@yourIP -pYourPort" or "ssh youruser@blockchain.yourDomain -pYourPort"
+        * ''ssh youruser@yourIP -pYourPort" or "ssh youruser@blockchain.yourDomain -pYourPort''
       * An example:
         * ''ssh ela@blockchain.elachain.cz -p10222 ''
-  - **Downloading the installation .deb package ****(replace ''<ACCESS_TOKEN>''  with received token):**
+  - **Downloading the installation .deb package ****(replace ''<ACCESS_TOKEN>'' with received token):**
-      * ''wget –header „PRIVATE-TOKEN: <ACCESS_TOKEN>“ „[[https://eu-de.git.cloud.ibm.com/api/v4/projects/27078/repository/files/elachain-preq.deb/raw|https://eu-de.git.cloud.ibm.com/api/v4/projects/27078/repository/files/elachain-preq.deb/raw]]“ -O ./elachain-preq.deb''
+       * <code>wget --header "PRIVATE-TOKEN: <ACCESS_TOKEN>" "https://eu-de.git.cloud.ibm.com/api/v4/projects/27078/repository/files/elachain-preq.deb/raw" -O ./elachain-preq.deb</code>
-  - **Check package integrity with **''sha256sum elachain-preq.deb'' ** command. Hash of the current package version is: **''f11fbe233a319139b1ec9e26f34e3eecc787b4534eee25015b95f7d16a8e76e3''
+  - **Check package integrity with **''sha256sum elachain-preq.deb'' ** command. Hash of the current package version is: **''69361ec77d08eca378c8af3f22cbe710b44fa62258e104683079cf17a67713d8''
   - **Run installation package **''sudo apt install ./elachain-preq.deb''  (you have to be in the directory where the package was downloaded)
   - **Run **''node_config'' ** command after the installation is complete **  (without sudo - you have to run this command as a newly created user)
@@ Řádek 28: / Řádek 28: @@
       * Next is a question about creating an Apache configuration. In most cases, it is desirable to choose "y". Choose the "n" option if you have enough experience with the Apache server configuration and you need a specific configuration. Learn more about Apache configuration [[:en_installation:apache|here]]
       * Then you need to fill in an email to generate an SSL certificate via Let's Encrypt. If you want to use your own SSL certificate, you will need to add its path to ''/etc/apache2/sites-available/blockchain.yourDomain.conf''  after the installation is complete - more [[:en_installation:apache|here]]
-      * The last question concerns the installation of the logDNA service, which allows us to access script logs remotely. To confirm this, enter "y" again
+      * The last question concerns the installation of the logging service, which allows us to access script logs remotely. To confirm this, enter "y" again
-        * Installation of the logDNA service is also possible later by calling ''setLogDNA''
+        * Installation of the logging service is also possible later by calling ''install_ibm_logs''
   - **After completing **''node_config'' **, it is advisable to restart the computer or relogin the user.**
       * Remotely: ''sudo reboot''
@@ Řádek 50: / Řádek 50: @@
       * When the gateway bootstrap you will be asked for the number of proxy servers due to the correct functionality of the endpoint limiter. If there are no proxy servers in front of the server, choose N. Otherwise, fill in their number + 1 (EBS setup adds one by itself).
   - **Installation is now finished. When listing docker containers using **''docker ps'' **, the following containers should be visible:**
->  gateway.blockchain.yourDomain couchdb-gateway.blockchain.yourDomain apps-notarius apps-admin apps-admin-mongo ebs-peer0.blockchain.yourDomain-notarius_cc-"version" ebs-peer0.blockchain.yourDomain-admin_cc-"version" ebs-peer1.blockchain.yourDomain-notarius_cc-"version" ebs-peer1.blockchain.yourDomain-admin_cc-"version" cli peer0.blockchain.yourDomain peer1.blockchain.yourDomain gtw-ca.blockchain.yourDomain couchdb0 couchdb1 monitoring-telegraf
+<code>
+gateway.blockchain.yourDomain
+couchdb-gateway.blockchain.yourDomain
+apps-notarius
+apps-admin
+apps-admin-mongo
+ebs-peer0.blockchain.yourDomain-notarius_cc-"version"
+ebs-peer0.blockchain.yourDomain-admin_cc-"version"
+ebs-peer1.blockchain.yourDomain-notarius_cc-"version"
+ebs-peer1.blockchain.yourDomain-admin_cc-"version"
+cli
+peer0.blockchain.yourDomain
+peer1.blockchain.yourDomain
+gtw-ca.blockchain.yourDomain
+couchdb0
+couchdb1
+monitoring-telegraf
+</code>
   * If the apache server is running correctly at the same time, you can open Notarius application running on your node at the address [[https://blockchain.yourDomain|https://blockchain.yourDomain]]
   * The Admin application can then be found under [[https://blockchain.yourDomain/admin|https://blockchain.yourDomain/admin]]