nearxos/reterminal-dm4
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update FILE_SERVER URL in first-boot scripts and documentation

Browse Source 
Change the default FILE_SERVER URL from `http://10.130.60.141:5000/files/first-boot` to `http://10.20.50.1:5000/files/first-boot` across multiple files, including the first-boot script, documentation, and example user data. This update ensures consistency in asset retrieval for first-boot operations.
This commit is contained in:
nearxos
2026-02-21 20:43:06 +02:00
parent 595ae0dd35
commit 3909fd7cf1
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
emmc-provisioning/cloud-init/config-files/README.md
View File

@@ -1,6 +1,6 @@
# Config files for first-boot (file server)
first-boot.sh downloads these from `FILE_SERVER` (e.g. `http://10.130.60.141:5000/files/first-boot`) and installs them to the paths below. Upload each file into the **first-boot** subfolder of portal-files (e.g. `/var/lib/cm4-provisioning/portal-files/first-boot/`).
first-boot.sh downloads these from `FILE_SERVER` (e.g. `http://10.20.50.1:5000/files/first-boot`) and installs them to the paths below. Upload each file into the **first-boot** subfolder of portal-files (e.g. `/var/lib/cm4-provisioning/portal-files/first-boot/`).
| File on server | Destination on device |
|----------------|------------------------|

2
emmc-provisioning/cloud-init/files-from-guard/README.md
View File

@@ -1,6 +1,6 @@
# Files for the file server
first-boot.sh downloads from **`.../files/first-boot/`** (e.g. `http://10.130.60.141:5000/files/first-boot`). Put all first-boot assets in a **first-boot** subfolder of portal-files so provisioning works.
first-boot.sh downloads from **`.../files/first-boot/`** (e.g. `http://10.20.50.1:5000/files/first-boot`). Put all first-boot assets in a **first-boot** subfolder of portal-files so provisioning works.
## Required files (host under `.../files/first-boot/`)

4
emmc-provisioning/cloud-init/first-boot.md
View File

@@ -66,7 +66,7 @@ Creates `/home/pi/.config/autostart` so that `.desktop` files placed there are s
Downloads from `FILE_SERVER` (no local creation):
- **`FILE_SERVER`** — Base URL for first-boot assets (default: `http://10.130.60.141:5000/files/first-boot`). All first-boot files are served from a **first-boot** subfolder on the file server. Change this if your server or path is different.
- **`FILE_SERVER`** — Base URL for first-boot assets (default: `http://10.20.50.1:5000/files/first-boot`). All first-boot files are served from a **first-boot** subfolder on the file server. Change this if your server or path is different.
- **`start-chromium.sh`** — Downloaded to `/home/pi/start-chromium.sh`, made executable (755), owned by `pi`. Waits for the desktop, then starts Chromium in fullscreen. When the session is Wayland (rpd-labwc), Chromium runs with `--ozone-platform=wayland` so **touch long-press produces right-click (context menu)** like the rest of the desktop; on X11 it falls back to `--ozone-platform=x11` and uses `wmctrl` to force fullscreen.
- **`chromium-kiosk.desktop`** — Downloaded to `/home/pi/.config/autostart/chromium-kiosk.desktop`, mode 644, owned by `pi`. This autostart entry runs `start-chromium.sh` when `pi` logs in.
@@ -78,7 +78,7 @@ Ensure the `.desktop` file on the server has `Exec=/home/pi/start-chromium.sh` (
## Boot splash and wallpaper (single image from file server)
A **single image** (`splash.png`) is used for the boot splash, login screen, and desktop wallpaper. Host it at **`${FILE_SERVER}/splash.png`** (e.g. `http://10.130.60.141:5000/files/splash.png`).
A **single image** (`splash.png`) is used for the boot splash, login screen, and desktop wallpaper. Host it at **`${FILE_SERVER}/splash.png`** (e.g. `http://10.20.50.1:5000/files/splash.png`).
- **Plymouth (boot splash):** Downloads `splash.png`, `custom.plymouth`, and `custom.script` from the file server → installs to `/usr/share/plymouth/themes/custom/` → sets `Theme=custom` in `/etc/plymouth/plymouthd.conf` (single `[Daemon]` section) → runs `update-initramfs -u`. If any download fails, logs a warning and continues. **Note:** On reTerminal DM the DSI panel can initialize a few seconds into boot, so the Plymouth splash may appear briefly or after a short black screen; this is normal for DSI displays.
- **LightDM (login screen):** Copies the same image to `/usr/share/rpd-wallpaper/splash.png` and writes `/etc/lightdm/lightdm.conf.d/99-wallpaper.conf` with `wallpaper=...` and `wallpaper_mode=crop`.

2
emmc-provisioning/cloud-init/first-boot.sh
View File

@@ -7,7 +7,7 @@ export DEBIAN_FRONTEND=noninteractive
# --- Constants ---
# All first-boot assets live in portal-files/first-boot/ on the file server.
FILE_SERVER="http://10.130.60.141:5000/files/first-boot"
FILE_SERVER="http://10.20.50.1:5000/files/first-boot"
HOSTNAME="guard"
PI_USER="pi"
PI_HOME="/home/$PI_USER"

2
emmc-provisioning/cloud-init/user-data-remote-gnss.example
View File

@@ -30,7 +30,7 @@ write_files:
runcmd:
- systemctl enable ssh
- systemctl start ssh
- curl -fsSL "http://10.130.60.141:5000/files/first-boot.sh" -o /tmp/first-boot.sh
- curl -fsSL "http://10.20.50.1:5000/files/first-boot.sh" -o /tmp/first-boot.sh
- chmod +x /tmp/first-boot.sh
- /tmp/first-boot.sh
# - rm -f /tmp/first-boot.sh