Obě strany předchozí revizePředchozí verze | |
en_installation:installation_guide [2023/12/02 22:30] – [Installation guide:] kozak | en_installation:installation_guide [2025/01/10 14:00] (aktuální) – [Installation guide:] kozak |
---|
- **Downloading the installation .deb package ****(replace ''<ACCESS_TOKEN>'' with received token):** | - **Downloading the installation .deb package ****(replace ''<ACCESS_TOKEN>'' with received token):** |
* <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> | * <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: **''d28e2062252860e724d2f511e257feffa2b2b295bd62d35ee8d5d3900bd6ba3e'' | - **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 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) | - **Run **''node_config'' ** command after the installation is complete ** (without sudo - you have to run this command as a newly created user) |
* 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]] | * 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]] | * 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.** | - **After completing **''node_config'' **, it is advisable to restart the computer or relogin the user.** |
* Remotely: ''sudo reboot'' | * Remotely: ''sudo reboot'' |