🤖 I have created a release *beep* *boop* --- ## [4.2.0](https://github.com/unraid/api/compare/v4.1.3...v4.2.0) (2025-03-18) ### Features * add resolver for logging ([#1222](https://github.com/unraid/api/issues/1222)) ([3f590c5](3f590c56e3)) * connect settings web component ([#1211](https://github.com/unraid/api/issues/1211)) ([acbf46d](acbf46df3f)) * improve local dev with install path ([#1221](https://github.com/unraid/api/issues/1221)) ([ce61fee](ce61fee41c)) * split plugin builds ([d63e54b](d63e54bdbc)) * swap to absolute paths for css ([#1224](https://github.com/unraid/api/issues/1224)) ([dd9983c](dd9983c8b7)) * update theme application logic and color picker ([#1181](https://github.com/unraid/api/issues/1181)) ([a030626](a0306269c6)) * use patch version if needed on update check ([#1227](https://github.com/unraid/api/issues/1227)) ([12e16a6](12e16a6404)) ### Bug Fixes * add INELIGIBLE state to ConfigErrorState enum ([#1220](https://github.com/unraid/api/issues/1220)) ([0f550f9](0f550f9d94)) * **api:** dynamix notifications dir during development ([#1216](https://github.com/unraid/api/issues/1216)) ([2700722](270072266a)) * **api:** type imports from generated graphql types ([#1215](https://github.com/unraid/api/issues/1215)) ([bce06cd](bce06cd76c)) * **deps:** update dependency @nestjs/schedule to v5 ([#1197](https://github.com/unraid/api/issues/1197)) ([85c8ef5](85c8ef53ad)) * **deps:** update dependency @vueuse/core to v12 ([#1199](https://github.com/unraid/api/issues/1199)) ([ff8eba3](ff8eba3df5)) * fix changelog thing again ([a9d5ca8](a9d5ca8899)) * fix invalid path to node with sh execution ([#1213](https://github.com/unraid/api/issues/1213)) ([f1838bf](f1838bf69a)) * load tag correctly ([b24a575](b24a575cbb)) * log errors ([365dcae](365dcae04b)) * one-command dev & web env files ([#1214](https://github.com/unraid/api/issues/1214)) ([4641894](4641894240)) * re-release fixed ([b491590](b49159022d)) * recreate watcher on path change ([#1203](https://github.com/unraid/api/issues/1203)) ([bde37d6](bde37d6751)) * update brand loading variants for consistent sizing ([#1223](https://github.com/unraid/api/issues/1223)) ([1b0fbaf](1b0fbaf81a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Unraid Plugin Builder
Tool for building and testing Unraid plugins locally as well as packaging them for deployment.
Development Workflow
1. Watch for Changes
The watch command will automatically sync changes from the API, UI components, and web app into the plugin source:
# Start watching all components
pnpm run watch:all
# Or run individual watchers:
pnpm run api:watch # Watch API changes
pnpm run ui:watch # Watch Unraid UI component changes
pnpm run wc:watch # Watch web component changes
This will copy:
- API files to
./source/dynamix.unraid.net/usr/local/unraid-api - UI components to
./source/dynamix.unraid.net/usr/local/emhttp/plugins/dynamix.my.servers/unraid-components - Web components to the same UI directory
2. Build the Plugin
Once your changes are ready, build the plugin package:
# Build using Docker - on non-Linux systems
pnpm run docker:build-and-run
# Or build with the build script
pnpm run build:validate
This will create the plugin files in ./deploy/release/
3. Serve and Install
Start a local HTTP server to serve the plugin files:
# Serve the plugin files
pnpm run http-server
Then install the plugin on your Unraid development machine by visiting:
http://SERVER_NAME.local/Plugins
Then paste the following URL into the Unraid Plugins page:
http://YOUR_LOCAL_DEV_MACHINE_IP:8080/plugins/local/dynamix.unraid.net.plg
Replace SERVER_NAME with your development machine's hostname.
Development Tips
- Run watchers in a separate terminal while developing
- The http-server includes CORS headers for local development
- Check the Unraid system log for plugin installation issues
Environment Setup
-
Initialize environment:
pnpm run env:init -
Validate environment:
pnpm run env:validate
Available Commands
Build Commands
build- Build the plugin packagebuild:validate- Build with environment validationdocker:build- Build the Docker containerdocker:run- Run the builder in Dockerdocker:build-and-run- Build and run in Docker
Watch Commands
watch:all- Watch all component changesapi:watch- Watch API changesui:watch- Watch UI component changeswc:watch- Watch web component changes
Server Commands
http-server- Serve the plugin files locally
Environment Commands
env:init- Create initial .env fileenv:validate- Validate environment setupenv:clean- Remove .env file
Troubleshooting
-
Watch not updating files
- Check that source directories exist
- Verify file permissions
-
Build failures
- Ensure .env file exists
- Check Docker setup if using containerized build
- Verify source files are present
-
Installation issues
- Confirm http-server is running
- Check your local IP is correct
- Verify plugin file permissions