Difference between revisions of "BoS Telegram AutoStart"
Jump to navigation
Jump to search
(Prepared the page for translation) |
(Marked this version for translation) |
||
| Line 2: | Line 2: | ||
<translate> | <translate> | ||
==Creating BoS Telegram AutoStart== | ==Creating BoS Telegram AutoStart== <!--T:1--> | ||
<!--T:2--> | |||
The following guide works on every linux distribution with the Systemd Software Manager Tool. I tested in with a Raspiblitz setup, but if you follow the installation process of the BoS tool, it should also work without problems on umbrel. | The following guide works on every linux distribution with the Systemd Software Manager Tool. I tested in with a Raspiblitz setup, but if you follow the installation process of the BoS tool, it should also work without problems on umbrel. | ||
(Everything can also be found in my git repo [https://github.com/ziggie1984/miscellanous.git gitrepo]). | (Everything can also be found in my git repo [https://github.com/ziggie1984/miscellanous.git gitrepo]). | ||
===Prerequesties=== | ===Prerequesties=== <!--T:3--> | ||
<!--T:4--> | |||
BoS has already been installed and an initial connection with your telegram bot has been established. Because if we want to put the bos telegram connection into the startup routine the API-Key of the Bot should already been entered. | BoS has already been installed and an initial connection with your telegram bot has been established. Because if we want to put the bos telegram connection into the startup routine the API-Key of the Bot should already been entered. | ||
===Checklist for Raspiblitz=== | ===Checklist for Raspiblitz=== <!--T:5--> | ||
<!--T:6--> | |||
* Login via ssh: <code> ssh admin@ip.ip.ip.ip </code> | * Login via ssh: <code> ssh admin@ip.ip.ip.ip </code> | ||
* Change to the following directory: <code> cd /etc/systemd/system/ </code> | * Change to the following directory: <code> cd /etc/systemd/system/ </code> | ||
| Line 30: | Line 33: | ||
<!--T:7--> | |||
[Service] | [Service] | ||
ExecStart=/home/bos/.npm-global/bin/bos telegram --connect VERBINDUNGSCODE | ExecStart=/home/bos/.npm-global/bin/bos telegram --connect VERBINDUNGSCODE | ||
| Line 39: | Line 43: | ||
StandardError=journal | StandardError=journal | ||
<!--T:8--> | |||
[Install] | [Install] | ||
WantedBy=multi-user.target </code> | WantedBy=multi-user.target </code> | ||
| Line 46: | Line 51: | ||
* wait until your telegram bot shows the new connection to check whether the service is running properly you can type: sudo systemctl status bos-telegram.service. Remember lighting needs to be up and unlocked before the bot is able to start. | * wait until your telegram bot shows the new connection to check whether the service is running properly you can type: sudo systemctl status bos-telegram.service. Remember lighting needs to be up and unlocked before the bot is able to start. | ||
<!--T:9--> | |||
''Please give a feedback on Telegram if the guide worked for you with umbrel, @ziggiesmoke'' | ''Please give a feedback on Telegram if the guide worked for you with umbrel, @ziggiesmoke'' | ||
</translate> | </translate> | ||
Revision as of 19:46, 2 October 2021
Creating BoS Telegram AutoStart
The following guide works on every linux distribution with the Systemd Software Manager Tool. I tested in with a Raspiblitz setup, but if you follow the installation process of the BoS tool, it should also work without problems on umbrel. (Everything can also be found in my git repo gitrepo).
Prerequesties
BoS has already been installed and an initial connection with your telegram bot has been established. Because if we want to put the bos telegram connection into the startup routine the API-Key of the Bot should already been entered.
Checklist for Raspiblitz
- Login via ssh:
ssh admin@ip.ip.ip.ip - Change to the following directory:
cd /etc/systemd/system/ - Create a so called unit-file:
sudo touch bos-telegram.service - open file with:
sudo nano bos-telegram.service - copy the following content into it, change CONNECTIONCODE with your own code:
#Systemd unit for Bos-Telegram Bot #/etc/systemd/system/bos-telegram.service [Unit] Description=bos-telegram Wants=lnd.service After=lnd.service [Service] ExecStart=/home/bos/.npm-global/bin/bos telegram --connect VERBINDUNGSCODE User=bos Restart=always TimeoutSec=120 RestartSec=30 StandardOutput=null StandardError=journal [Install] WantedBy=multi-user.target </code>
- Save file and then type the following command in the terminal: sudo systemctl enable bos-telegram.service
- Reboot your node
- wait until your telegram bot shows the new connection to check whether the service is running properly you can type: sudo systemctl status bos-telegram.service. Remember lighting needs to be up and unlocked before the bot is able to start.
Please give a feedback on Telegram if the guide worked for you with umbrel, @ziggiesmoke