Skip to content
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.

Latest commit

 

History

History
65 lines (44 loc) · 1.86 KB

File metadata and controls

65 lines (44 loc) · 1.86 KB

RTL

Note: v0.15.0 of RTL has breaking changes, this playbook needs updating.

  • create a file with the rune: echo "LIGHTNING_RUNE=\"$(lightning-cli commando-rune | jq -r .rune)\"" > .rune
  • configure the rune path in RTL
  • the RTL-config.json in /var/compose is spurious, iirc this pod is using env variables
  • we probably dont need a macaroon anymore with clnrest

Ride-The-Lightning/RTL

This deployment has extra steps due to handling sensitive macaroon material. Upgrades are a single command though.

variables

See host_vars

deployment example

  • Generate an app password and source it into the environment. Then run the setup tasks.
pass generate -n satstack.net/wartortle/RTL_PASS
export wartortle_RTL_PASSWORD=$(pass satstack.net/wartortle/RTL_PASS)
ansible-playbook playbooks/host_tasks/wartortle.satstack.net/rtl.yml --tags setup
  • Copy the sensitive access.macaroon (which is a plaintext admin macaroon) from your cl-rest to /var/compose/.secrets/lightningd/

  • Run the rest of the play and let systemd start the container

    ansible-playbook playbooks/host_tasks/wartortle.satstack.net/rtl.yml
    systemctl --user restart container-RTL.service
    podman logs --follow RTL
    

systemd

systemctl --user status container-RTL.service

upgrades

ansible-playbook playbooks/host_tasks/wartortle.satstack.net/rtl/main.yml --tags podman

troubleshooting

podman inspect RTL | jq

Drop this in your bashrc:

repod() {
    systemctl --user restart "container-${1}.service"
    podman logs --tail=0 --follow $1
}

Then you get nice output when you repod RTL.