[Script request]: Standalone WindFront frontend for Zigbee2MQTT

[Nerivec]

Application Name

zigbee2mqtt-windfront

Website

https://github.com/Nerivec/zigbee2mqtt-windfront/wiki#standalone-serving-with-multi-zigbee2mqtt-support

Description

@MickLesk it should look something like this:

#!/usr/bin/env bash

source /dev/stdin <<<"$FUNCTIONS_FILE_PATH"
color
verb_ip6
catch_errors
setting_up_container
network_check
update_os

msg_info "Installing Dependencies"
$STD apt-get install -y nginx
msg_ok "Installed Dependencies"

NODE_VERSION="22" setup_nodejs

fetch_and_deploy_gh_release "WindFront" "Nerivec/zigbee2mqtt-windfront" "tarball" "latest" "/opt/zigbee2mqtt-windfront"

read -rp "Enter the Zigbee2MQTT API URLs (comma-separated): " VITE_Z2M_API_URLS
read -rp "Enter the names for the previous URLs (comma-separated, same order): " VITE_Z2M_API_NAMES

msg_info "Building WindFront"
cd /opt/zigbee2mqtt-windfront
$STD npm ci
$STD NODE_ENV=production VITE_Z2M_API_URLS="$VITE_Z2M_API_URLS" VITE_Z2M_API_NAMES="$VITE_Z2M_API_NAMES" npm run build
msg_ok "Built WindFront"

msg_info "Configure Nginx"
rm -rf /usr/share/nginx/html
ln -s /opt/zigbee2mqtt-windfront/dist /usr/share/nginx/html
systemctl restart nginx
msg_ok "Configured Nginx"

motd_ssh
customize

msg_info "Cleaning up"
$STD apt-get -y autoremove
$STD apt-get -y autoclean
msg_ok "Cleaned"

This setup is very basic, same as the Docker container.
Might need some tweaking to better fit Proxmox (which I'm not familiar with).
Maybe remove nodejs & co after the build is done to clean things up?
Could cp the dist dir and remove the repo too (large node_modules)?

This method of install has not been tested at all at this time. I don't have a setup for it.

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.

[MickLesk]

Isnt better, to build an prebuild package like Pulse? Its smarter, faster and dont need npm builds

https://github.com/rcourtman/Pulse

[Nerivec]

The build relies on the envs, defined by the user (baked in).
I suppose we could do it like the Docker container (envsubst triggered on container start), but I'm not sure what's your preferred approach in here (or what's doable really...).
https://github.com/Nerivec/zigbee2mqtt-windfront/blob/main/Dockerfile#L20

[Nerivec]

I've included a tarball release with latest version, if you want to play with this. 😬
You'll have to trigger the env substitution like the Docker container does.

• Set the envs Z2M_API_URLS and Z2M_API_NAMES
• Then trigger the equivalent of https://github.com/Nerivec/zigbee2mqtt-windfront/blob/main/.docker/scripts/100-envsubst-on-app-envs.sh

The difference with the build method? The build method bakes the values into the code directly, while the envsubst method replaces template variables in the built dist (this allows to cover baremetal & container scenario).