mirror of
https://github.com/rootzoll/raspiblitz.git
synced 2025-02-28 16:58:03 +01:00
misc updates for v1.10.0rc1 (#4001)
* add lndg update info * mark v1.10.0rc1 version * Thunderhub v0.13.19 * changing default repo to raspiblitz org * LNbits 0.10.9 * lnbits dont delete user on "off" * BTCPayServer 1.10.3 * switch default branch to v1.10
This commit is contained in:
/rootzoll
GitHub
parent
50fbeb0168
commit
9878ea8a02
9 changed files with 30 additions and 29 deletions
|
|
@ -6,6 +6,10 @@
|
|||
- Update: Core Lightning v23.05.2 [details](https://github.com/ElementsProject/lightning/releases/tag/v23.05.2)
|
||||
- Update: Electrum Server in Rust (electrs) v0.9.14 [details](https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#0914-jun-10-2023)
|
||||
- Update: Lightning Terminal v0.10.1-alpha [details](https://github.com/lightninglabs/lightning-terminal/releases/tag/v0.10.1-alpha)
|
||||
- Update: LNDg v1.7.0 [details](https://github.com/cryptosharks131/lndg)
|
||||
- Update: Thunderhub v0.13.19 [details](https://github.com/apotdevin/thunderhub/releases/tag/v0.13.19)
|
||||
- Update: LNbits 0.10.9 [details](https://github.com/lnbits/lnbits/releases/tag/0.10.9)
|
||||
- Update: BTCPayServer 1.10.3 (postgres by default with sqlite migration) [details](https://github.com/btcpayserver/btcpayserver/releases/tag/v1.10.3)
|
||||
- Fix: Homebanking Interface FinTS/HBCI (experimental) [details](https://github.com/rootzoll/raspiblitz/issues/1186)
|
||||
|
||||
## What's new in Version 1.9.0 of RaspiBlitz?
|
||||
|
|
|
|||
|
|
@ -82,5 +82,5 @@ Reviewers that have demonstrated a deeper commitment and understanding of the pr
|
|||
The project leader is the release manager for each RaspiBlitz release.
|
||||
|
||||
## Copyright
|
||||
By contributing to this repository, you agree to license your work under the [MIT license](https://github.com/rootzoll/raspiblitz/blob/master/LICENSE).
|
||||
By contributing to this repository, you agree to license your work under the [MIT license](https://github.com/raspiblitz/raspiblitz/blob/master/LICENSE).
|
||||
Any work contributed where you are not the original author must contain its license header with the original author(s) and source.
|
||||
|
|
|
|||
12
FAQ.dev.md
12
FAQ.dev.md
|
|
@ -32,7 +32,7 @@ Creating the base minimal sd card:
|
|||
* In terminal `ssh pi@[IP-OF-RASPIBLITZ]`
|
||||
* Password is `raspberry`
|
||||
* Run the following command BUT REPLACE `[BRANCH]` with the branch-string of your latest version
|
||||
* To run the minimal pack: `wget --no-cache https://raw.githubusercontent.com/rootzoll/raspiblitz/[BRANCH]/build_sdcard.sh && sudo bash build_sdcard.sh -u rootzoll -b [BRANCH] -f 0 -d headless`
|
||||
* To run the minimal pack: `wget --no-cache https://raw.githubusercontent.com/raspiblitz/raspiblitz/[BRANCH]/build_sdcard.sh && sudo bash build_sdcard.sh -u raspiblitz -b [BRANCH] -f 0 -d headless`
|
||||
* Monitor/Check outputs for warnings/errors
|
||||
* Login new with `ssh admin@[IP-OF-RASPIBLITZ]` (pw: raspiblitz) and run `release`
|
||||
* Disconnect WiFi/LAN on build laptop (hardware switch off) and shutdown
|
||||
|
|
@ -143,7 +143,7 @@ To build a SD card image from another branch than master, you follow the [Build
|
|||
|
||||
For example if you want to make a build from the 'dev' branch you execute the following command:
|
||||
|
||||
`wget --no-cache https://raw.githubusercontent.com/rootzoll/raspiblitz/dev/build_sdcard.sh && sudo bash build_sdcard.sh -b dev`
|
||||
`wget --no-cache https://raw.githubusercontent.com/raspiblitz/raspiblitz/dev/build_sdcard.sh && sudo bash build_sdcard.sh -b dev`
|
||||
|
||||
If you want to see all the optional parameters for building your sd card, just answere `no` on first question and call `sudo bash build_sdcard.sh --help`.
|
||||
|
||||
|
|
@ -161,7 +161,7 @@ If you are then working in your forked repo and want to update the scripts on yo
|
|||
|
||||
### How can I checkout a new branch from the RaspiBlitz repo to my forked repo?
|
||||
|
||||
You need to have your forked repo checked-out on your laptop. There your should see your forked repo as `origin` when you run `git remote -v`. If you don't see an additional `upstream` remote yet, then create it with the following command: `git remote add upstream https://github.com/rootzoll/raspiblitz.git`.
|
||||
You need to have your forked repo checked-out on your laptop. There your should see your forked repo as `origin` when you run `git remote -v`. If you don't see an additional `upstream` remote yet, then create it with the following command: `git remote add upstream https://github.com/raspiblitz/raspiblitz.git`.
|
||||
|
||||
So, first checkout the new branch named `BRANCH` from the original RaspBlitz repo to your local computer with: `git fetch upstream` and then `git checkout -b BRANCH upstream/BRANCH`.
|
||||
|
||||
|
|
@ -173,7 +173,7 @@ Once the branch is available and synced between the RaspiBlitz GitHub repo, your
|
|||
|
||||
Since v1.5 of RaspiBlitz there has been an easy way thru the SSH menus: Under `MAIN MENU > UPDATE > PATCH` you have the option to change the GitHub repository and and branch to sync with. You change the GitHub Reposity by setting the GitHub username where you forked the Repo.
|
||||
|
||||
So for example: If you forked the RaspiBlitz project (rootzoll/raspiblitz) on GitHub and your GitHub project page is now called: https://github.com/raumi75/raspiblitz ... then just change the repo to sync/patch with to your username `raumi75`.
|
||||
So for example: If you forked the RaspiBlitz project (raspiblitz/raspiblitz) on GitHub and your GitHub project page is now called: https://github.com/raumi75/raspiblitz ... then just change the repo to sync/patch with to your username `raumi75`.
|
||||
|
||||
Now you can use the `Patch/Sync RaspiBlitz with GitHub Repo` to easily keep your RaspiBlitz in sync with your forked repository and develop your own customizations and features.
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ So your workflow can go like this: You write code on your local computer. Commit
|
|||
|
||||
### How to add an app to the RaspiBlitz?
|
||||
|
||||
To add your app you can fork the raspiblitz repo, follow the `/home.admin/config.scripts/bonus.template.sh` script [see code](https://github.com/rootzoll/raspiblitz/blob/dev/home.admin/config.scripts/bonus.template.sh), copy/adapt it, test it on your RaspiBlitz and make a PR back to the main repo.
|
||||
To add your app you can fork the raspiblitz repo, follow the `/home.admin/config.scripts/bonus.template.sh` script [see code](https://github.com/raspiblitz/raspiblitz/blob/dev/home.admin/config.scripts/bonus.template.sh), copy/adapt it, test it on your RaspiBlitz and make a PR back to the main repo.
|
||||
|
||||
### How contribute a feature/change from my forked branch back to the RaspiBlitz repo?
|
||||
|
||||
|
|
@ -239,7 +239,7 @@ just notes so far:
|
|||
|
||||
https://brew.sh
|
||||
brew install qemu
|
||||
https://github.com/rootzoll/raspiblitz/actions --> download amd64-lean image
|
||||
https://github.com/raspiblitz/raspiblitz/actions --> download amd64-lean image
|
||||
double unzip until `qcow2` file
|
||||
convert `qcow2` to `vdi:
|
||||
qemu-img convert -f qcow2 raspiblitz-amd64-debian-lean.qcow2 -O vdi raspiblitz-amd64-debian-lean.vdi
|
||||
|
|
|
|||
12
FAQ.md
12
FAQ.md
|
|
@ -121,7 +121,7 @@ The upgrade should be quite simple - you don't need to close any channels:
|
|||
|
||||
- It would be best to get a second 16GB or 32GB SD card - but you can also reuse your old one
|
||||
- In the SSH main menu of you RaspiBlitz choose `UPDATE` & follow the dialogs until shutdown
|
||||
- Download the new RaspiBlitz image file from the [GitHub README](https://github.com/rootzoll/raspiblitz/blob/dev/README.md#installing-the-software)
|
||||
- Download the new RaspiBlitz image file from the [GitHub README](https://github.com/raspiblitz/raspiblitz/blob/dev/README.md#installing-the-software)
|
||||
- Write the new image to the (new) SD card with a tool like [balena etcher](https://www.balena.io/etcher/)
|
||||
- RaspiBlitz with new SD card image - it now goes through a recover/update phase - this may take some time.
|
||||
- Once that's done, login once via SSH and use the password raspiblitz and set a new password A (can be your old one or a new one).
|
||||
|
|
@ -180,7 +180,7 @@ If that doesn't work, try to ping the IP of the RaspiBlitz with `ping [IP-of-Ras
|
|||
- Check if you have a VPN running on your laptop - some VPNs block local network
|
||||
- Some Routers have `IP Isolation` switched on - not allowing two devices to connect
|
||||
|
||||
If you've checked those and SSH is still not working: Join the conversation on [GitHub Issue #420](https://github.com/rootzoll/raspiblitz/issues/420).
|
||||
If you've checked those and SSH is still not working: Join the conversation on [GitHub Issue #420](https://github.com/raspiblitz/raspiblitz/issues/420).
|
||||
|
||||
### How to SSH over Tor?
|
||||
|
||||
|
|
@ -363,7 +363,7 @@ There are two ways of performing a Backup:
|
|||
#### 1) Securing your On-Chain- and Channel-Funds during Operation
|
||||
|
||||
This is best done by auto backing-up the 'channel.backup' file to a remote location. But it just secures the funds you have in your on-chain wallet or in your channels. On recovery the channels will get closed. For details on how to setup see the README:
|
||||
https://github.com/rootzoll/raspiblitz/blob/v1.2/README.md#backup-for-on-chain---channel-funds
|
||||
https://github.com/raspiblitz/raspiblitz/blob/v1.2/README.md#backup-for-on-chain---channel-funds
|
||||
|
||||
#### 2) Making a complete LND data backup
|
||||
|
||||
|
|
@ -418,7 +418,7 @@ Then give LND some time to re-scan the blockchain. In the end you will have rest
|
|||
If you don't have the `channel.backup` file but only the seed words there is a last hope - read this article:
|
||||
https://medium.com/@guggero/did-you-lose-funds-on-the-lightning-network-because-of-a-disk-crash-8971b6a92494
|
||||
|
||||
*Important: If you see a zero balance for on-chain funds after restoring from seed ... see details discussed [here](https://github.com/rootzoll/raspiblitz/issues/278) - you might try setup fresh this time with bigger look-ahead number.*
|
||||
*Important: If you see a zero balance for on-chain funds after restoring from seed ... see details discussed [here](https://github.com/raspiblitz/raspiblitz/issues/278) - you might try setup fresh this time with bigger look-ahead number.*
|
||||
|
||||
|
||||
### How do I move funds & channels from RaspiBlitz to LND Lightning Desktop App?
|
||||
|
|
@ -450,7 +450,7 @@ Use the "Change Name/Alias of Node" option in the Lightning - LND Wallet Options
|
|||
|
||||
### How do I change the public port LND/Lightning node is running on?
|
||||
|
||||
There is a experimental script you can call from the terminal that will make all changes for you ... see details here: https://github.com/rootzoll/raspiblitz/issues/100#issuecomment-466722712
|
||||
There is a experimental script you can call from the terminal that will make all changes for you ... see details here: https://github.com/raspiblitz/raspiblitz/issues/100#issuecomment-466722712
|
||||
|
||||
### How do I solve a "signature mismatch after caveat verification" error?
|
||||
|
||||
|
|
@ -642,7 +642,7 @@ Yes but you need to change the port number (for example to 9736) on at least one
|
|||
|
||||
### How can I enforce UASP mode for my SSD controller?
|
||||
|
||||
By default just tested & selected SSD encasings/controller are running enabled with UASP in RaspiBlitz. UASP brings a speed up for the SSD but also if not well supported by the SSD encasing/controller can lead to system halts. If you know for sure that your SSD encasing/controller is supporting UASP fully you can place a file called `uasp.force` on the sd card boot section after flashing the image with your laptop. See details or report errors on issue [#2488](https://github.com/rootzoll/raspiblitz/issues/2488)
|
||||
By default just tested & selected SSD encasings/controller are running enabled with UASP in RaspiBlitz. UASP brings a speed up for the SSD but also if not well supported by the SSD encasing/controller can lead to system halts. If you know for sure that your SSD encasing/controller is supporting UASP fully you can place a file called `uasp.force` on the sd card boot section after flashing the image with your laptop. See details or report errors on issue [#2488](https://github.com/raspiblitz/raspiblitz/issues/2488)
|
||||
|
||||
### I am facing maintenance/emergency mode on boot. How do I fix it?
|
||||
|
||||
|
|
|
|||
|
|
@ -9,8 +9,8 @@
|
|||
# setup fresh SD card with image above - login per SSH and run this script:
|
||||
##########################################################################
|
||||
|
||||
defaultRepo="rootzoll"
|
||||
defaultBranch="v1.9"
|
||||
defaultRepo="raspiblitz" #user that hosts a `raspiblitz` repo
|
||||
defaultBranch="v1.10"
|
||||
|
||||
defaultAPIuser="fusion44"
|
||||
defaultAPIrepo="blitz_api"
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
# RaspiBlitz Version - always [major].[main].[sub] (sub can be a string like '2rc1')
|
||||
codeVersion="1.9.0"
|
||||
codeVersion="1.10.0rc1"
|
||||
# keep last line with comment
|
||||
|
|
@ -3,9 +3,9 @@
|
|||
# Based on: https://gist.github.com/normandmickey/3f10fc077d15345fb469034e3697d0d0
|
||||
|
||||
# https://github.com/dgarage/NBXplorer/tags
|
||||
NBXplorerVersion="v2.3.62"
|
||||
NBXplorerVersion="v2.3.65"
|
||||
# https://github.com/btcpayserver/btcpayserver/releases
|
||||
BTCPayVersion="v1.9.3"
|
||||
BTCPayVersion="v1.10.3"
|
||||
|
||||
# command info
|
||||
if [ $# -eq 0 ] || [ "$1" = "-h" ] || [ "$1" = "-help" ]; then
|
||||
|
|
@ -405,17 +405,17 @@ if [ "$1" = "install" ]; then
|
|||
cd btcpayserver || exit 1
|
||||
sudo -u btcpay git reset --hard $BTCPayVersion
|
||||
#sudo -u btcpay /home/admin/config.scripts/blitz.git-verify.sh "web-flow" "https://github.com/web-flow.gpg" "4AEE18F83AFDEB23" || exit 1
|
||||
#PGPsigner="nicolasdorier"
|
||||
#PGPpubkeyLink="https://keybase.io/nicolasdorier/pgp_keys.asc"
|
||||
#PGPpubkeyFingerprint="AB4CFA9895ACA0DBE27F6B346618763EF09186FE"
|
||||
PGPsigner="nicolasdorier"
|
||||
PGPpubkeyLink="https://keybase.io/nicolasdorier/pgp_keys.asc"
|
||||
PGPpubkeyFingerprint="AB4CFA9895ACA0DBE27F6B346618763EF09186FE"
|
||||
# ---
|
||||
#PGPsigner="Kukks"
|
||||
#PGPpubkeyLink="https://github.com/${PGPsigner}.gpg"
|
||||
#PGPpubkeyFingerprint="8E5530D9D1C93097"
|
||||
# ---
|
||||
PGPsigner="web-flow"
|
||||
PGPpubkeyLink="https://github.com/web-flow.gpg"
|
||||
PGPpubkeyFingerprint="4AEE18F83AFDEB23"
|
||||
#PGPsigner="web-flow"
|
||||
#PGPpubkeyLink="https://github.com/web-flow.gpg"
|
||||
#PGPpubkeyFingerprint="4AEE18F83AFDEB23"
|
||||
|
||||
echo "# verify signature of ${PGPsigner}"
|
||||
sudo -u btcpay /home/admin/config.scripts/blitz.git-verify.sh "${PGPsigner}" "${PGPpubkeyLink}" "${PGPpubkeyFingerprint}" || exit 1
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
# https://github.com/lnbits/lnbits
|
||||
|
||||
# https://github.com/lnbits/lnbits/releases
|
||||
tag="0.10.6"
|
||||
tag="0.10.9"
|
||||
VERSION="${tag}"
|
||||
|
||||
# command info
|
||||
|
|
@ -1039,9 +1039,6 @@ if [ "$1" = "0" ] || [ "$1" = "off" ]; then
|
|||
echo "# keeping data"
|
||||
fi
|
||||
|
||||
echo "# Remove the lnbits user"
|
||||
sudo userdel -rf lnbits 2>/dev/null
|
||||
|
||||
# setting value in raspi blitz config
|
||||
/home/admin/config.scripts/blitz.conf.sh set LNBits "off"
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
#!/bin/bash
|
||||
|
||||
# https://github.com/apotdevin/thunderhub
|
||||
THUBVERSION="v0.13.16"
|
||||
THUBVERSION="v0.13.19"
|
||||
|
||||
# command info
|
||||
if [ $# -eq 0 ] || [ "$1" = "-h" ] || [ "$1" = "-help" ]; then
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue