-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bos command run on startup #9
Comments
I also found that even the telegram bot API key did not remain saved after node reboot. Can this be saved in any way or it must be set every reboot? |
I'm doing it this way:
This starts a tmux session. You can run any command from there and when you run |
@AaronDewes Does tmux solve previously stated problems? |
Hey @JMskch. Very good point. For now you could do it by editing PS: to edit |
Sorry @JMskch, I said something stupid. There is no So no, you can't do it for now. Unless you rebuild the Docker image yourself. |
Sorry @JMskch, I said something stupid. There is no So no, you can't do it for now. Unless you rebuild the Docker image yourself. |
@JMskch Added this feature in v0.1.7 https://lightningshell.app/history/#v0.1.7 Either wait for the official Umbrel update, or upgrade Lightning Shell yourself to v0.1.7. |
That was fast, many thanks. |
Hi @ibz, how to run commands for connecting bos telegram? when I use cli commands, which normally works like(dummy token and key) I tried many different commands...things like changing shebang and so on, but I cannot make it work. on_start.sh seems executing...tried with basic command echo to file, which worked on docker restart. |
I haven't tried running the telegram bot myself, so I can't answer this, but I will reopen this issue and hopefully somebody will reply. |
I'm also struggling with it, actually. Did you end up figuring it out @JMskch ? |
@jonathanalevi unfortunately not. |
To clarify ... the on_start.sh script does not resolve this issue. The problem is, BOS normal behavior is to retain the API key between reboots. For some reason, the LightningShell container is not remembering the API key after reboot. This is a problem, because BOS initiates API key through an interactive prompt which cannot be scripted (i.e. on_start.sh won't work). If this issue gets resolved (BOS remembers API key after reboot), then BOS connection could be automated with on_start.sh. BOS telegram bot is probably one of the most popular things to run on an LND node. (It's the only way I know of, to be notified of node activity). It would be really sweet if this worked on LightningShell, because it would save lots of Umbrel users the hassle of installing BOS manually. That said... sorry, I can't say what cause might be. |
I have now once again run into this issue - ln-shell forgets the telegram API key for BoS on reboot. @ibz any ideas on why this could be, or strategies we could use for a fix or workaround for this? |
Hello,
is there a way to run some command on the startup of the docker? e.g.
bos telegram --connect 1726156086 1> /tmp/bos.log 2>&1 & disown
to connect telegram bos and run it in the background? It would be best if the upgrade did not override this setting.
Thanks in advance.
The text was updated successfully, but these errors were encountered: