How to install a quick and dirty environment to test latest changes?

[FabienD74]

Hi,
In order to fetch latest changes and perform some tests, i'm trying to have a DEV environment.
To do so cloned my existing LXC with pulse. stopped the pulse service, then i created a bash :

#!/bin/bash
apt update
apt upgrade
apt install ca-certificates curl jq tar
apt install golang-go
apt install git
apt install npm
cd /root
echo "Git clone ? ( Y / N )"
select response in "Y" "N" "n"; do
    case $response in
        "Y" )
            git clone https://github.com/rcourtman/Pulse
            break
            ;;
        *)
            break
            ;;
    esac
done

cd Pulse

when i execute npm run dev:foreground:lab i have errors related to "vite":

[hot-dev] Loaded encryption key from /root/Pulse/tmp/dev-config/.encryption.key
[hot-dev] Starting backend health monitor...
[hot-dev] Starting backend file watcher...
[hot-dev] Starting frontend with hot-reload on port 5173...
[hot-dev] WARNING: No supported file watcher found (inotifywait or fswatch). Auto-rebuild disabled.
vite.config.ts (1:288) [UNRESOLVED_IMPORT] Could not resolve 'vite' in vite.config.ts

Do i need to install something else ????
THX

[FabienD74]

Oh, looks like my service "Pulse2MQTT" was able to retreive some info from pulse and publish them to MQTT....
Is this setup also using "/etc/pulse" for API keys??? That would be perfect in my case.... ;-) ;-)

[rcourtman]

The unresolved vite import means the locked frontend dependencies were never installed. From the repository root, use the versions in CONTRIBUTING.md (Go 1.26 and Node.js 20), then run:

npm ci
npm --prefix frontend-modern ci
npm run dev:foreground:lab

The development runtime uses tmp/dev-config by default; it does not read /etc/pulse. HOT_DEV_USE_PROD_DATA=true npm run dev:foreground:lab opts into /etc/pulse, but do not point the development runtime and the production service at that directory at the same time. A copied test data directory is the safer route for experiments.

Closing this setup question now that the missing dependency step is pinned down.