Difference between revisions of "BoS Telegram AutoStart"
Jump to navigation
Jump to search
(Added File for umbrel) |
|||
| Line 35: | Line 35: | ||
<!--T:7--> | <!--T:7--> | ||
[Service] | [Service] | ||
ExecStart=/home/bos/.npm-global/bin/bos telegram --connect | ExecStart=/home/bos/.npm-global/bin/bos telegram --connect CONNECTIONCODE | ||
User=bos | User=bos | ||
Restart=always | Restart=always | ||
| Line 47: | Line 47: | ||
WantedBy=multi-user.target | WantedBy=multi-user.target | ||
</pre> | </pre> | ||
* Save file and then type the following command in the terminal: sudo systemctl enable bos-telegram.service | * Save file and then type the following command in the terminal: <code> sudo systemctl enable bos-telegram.service </code> | ||
* Reboot your node | * Reboot your node or it also works without rebooting by using this command: <code> sudo systemctl start bos-telegram.service </code> | ||
* 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: | ====For Umbrel the file has some minor changes==== | ||
<pre> | |||
#Systemd unit for Bos-Telegram Bot | |||
#/etc/systemd/system/bos-telegram.service | |||
[Unit] | |||
Description=bos-telegram | |||
Wants=lnd.service | |||
After=lnd.service | |||
<!--T:10--> | |||
[Service] | |||
ExecStart=/home/umbrel/.npm-global/bin/bos telegram --connect CONNECTIONCODE | |||
User=umbrel | |||
Restart=always | |||
TimeoutSec=120 | |||
RestartSec=30 | |||
StandardOutput=null | |||
StandardError=journal | |||
</translate> | </translate> | ||
Revision as of 07:33, 6 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 CONNECTIONCODE User=bos Restart=always TimeoutSec=120 RestartSec=30 StandardOutput=null StandardError=journal [Install] WantedBy=multi-user.target
- Save file and then type the following command in the terminal:
sudo systemctl enable bos-telegram.service - Reboot your node or it also works without rebooting by using this command:
sudo systemctl start bos-telegram.service - 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.
For Umbrel the file has some minor changes
#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/umbrel/.npm-global/bin/bos telegram --connect CONNECTIONCODE User=umbrel Restart=always TimeoutSec=120 RestartSec=30 StandardOutput=null StandardError=journal