🧪 Nutify - [ 0.1.6/0.1.7.x ] Collaborative testing and development.

[DartSteven]

Hi everyone!!!

I'm actively working on Nutify and I would need your help to test some features, so as to ensure greater compatibility and stability across multiple environments.

In my local setup, with my two UPSs, everything works perfectly according to my requirements. But because of this, I am at risk of not noticing any bugs or problems that might arise in other scenarios.

🔄 What do I propose?

I would like to post test versions here, gather feedback and guidance on what to test, so that I can correct any problems before merging on the master branch with the stable version.

If everything works correctly for you too, then I can proceed with more confidence!

🆕 First feature to test. It will be ready soon.

The first new feature I am working on is a complete overhaul of the Docker container boot system:

• NUT will no longer be configured via docker-compose.
• On first startup, the user will be automatically redirected to a welcome page where they can configure everything via web interface

This new mode will greatly simplify the user experience, especially for those who do not want to edit files manually.

---

Anyone who feels like helping me out with testing is welcome! 💪

If anyone is willing to help me test these features, could you please let me know in the comments below so I can get in touch with you directly?

Feel free to write me in the comments or open an issue with feedback.

Thanks in advance to everyone!

[DartSteven]

ARM64 : dartsteven/test:arm64-0.1.6TEST1
AMD64 : dartsteven/test:amd64-0.1.6TEST1

New docker-compose.yaml :

services:
  nut:
    image: dartsteven/test:amd64-0.1.6TEST1  # or dartsteven/test:arm64-0.1.6TEST1
    container_name: Nutify
    privileged: true
    cap_add:
      - SYS_ADMIN
      - SYS_RAWIO
      - MKNOD
    devices:
      - /dev/bus/usb:/dev/bus/usb:rwm
    device_cgroup_rules:
      - 'c 189:* rwm'
    environment:
      - LOG=true
      - LOG_LEVEL=DEBUG
      - LOG_WERKZEUG=true
      - ENABLE_LOG_STARTUP=Y
      - SSL_ENABLED=true
    ports:
      - 3493:3493
      - 5050:5050
      - 443:443
    volumes:
      - ./Nutify/logs:/app/nutify/logs
      - ./Nutify/instance:/app/nutify/instance
      - ./Nutify/ssl:/app/ssl
      - ./Nutify/etc/nut:/etc/nut
    restart: always
    user: root

I’ve published the two images for testing. If anyone is willing to help verify that everything works correctly, I’d really appreciate it. Otherwise, I’ll go ahead and merge to master in a couple of days. Thanks, everyone!

[DartSteven]

🚀 Here we go with the second test!

AMD64 : dartsteven/test:amd64-0.1.6TEST2
AMD64 : dartsteven/test:arm64-0.1.6TEST2

I'm asking for your help to test the following new features:

• 📧 Amazon SES provider support (for those using it)

• 📥 Download JSON button, now available under Advanced Options

• ⚙️ Initial configuration variables section under Advanced Options

• 🔗 Webhook feature now extended with Discord support

• 🖥️ Mini system monitor widget to keep an eye on CPU and RAM usage

• 🚨 Alert modal in case of connection loss with the database or other critical events

• 🛑 Polling auto-stop mechanism: now the system detects anomalies when UPS becomes unreachable and stops polling to prevent weird behavior

---

• ** docker-cmpose.yaml

services:
  nut:
    image: dartsteven/test:amd64-0.1.6TEST2 
    container_name: Nutify
    privileged: true
    cap_add:
      - SYS_ADMIN
      - SYS_RAWIO
      - MKNOD
    devices:
      - /dev/bus/usb:/dev/bus/usb:rwm
    device_cgroup_rules:
      - 'c 189:* rwm'
    environment:
      - LOG=true
      - LOG_LEVEL=DEBUG
      - LOG_WERKZEUG=true
      - ENABLE_LOG_STARTUP=Y
      - SSL_ENABLED=true
    ports:
      - 3493:3493
      - 5050:5050
      - 443:443
    volumes:
      - ./Nutify/logs:/app/nutify/logs
      - ./Nutify/instance:/app/nutify/instance
      - ./Nutify/ssl:/app/ssl
      - ./Nutify/etc/nut:/etc/nut
    restart: always
    user: root

---

⚠️ Reminder:
This is a TEST version, please run it separately from your main installation to avoid compromising your data.
👉 Stop your current Nutify instance before starting this one.

🗃️ You can reuse your previous database, but you'll need to reconfigure the email settings manually.

🔐 Note:
In this version, the Encryption Key must be entered manually in the web interface. This is temporary — I’ve already decided that in the next (and final) pre-release before the official publication on the master branch, the key will be injected via docker-compose.

---

🧪 Please test all sections thoroughly, not just the new features!
🐞 If you find any bugs, report them in the BUG section, not here.
I'd like to keep this thread clean for TEST release announcements only.

🙏 Thanks everyone for your time and help!

[DartSteven]

new version TEST3
I added an additional check to change the usb permissions.

dartsteven/test:amd64-0.1.6TEST3
dartsteven/test:arm64-0.1.6TEST3

[DartSteven]

OK Guys,

this is it! RC01 ready with all the things I needed to do.
Please test it thoroughly, through and through.
Please run Nutify without any other Nutify instances, and in an empty directory with exactly this docker composer .

Tell me what you think and if you find any other bugs (hopefully not) 🙂

services:
  nut:
#    build: .
    image: dartsteven/test:amd64-0.1.6RC01
    container_name: Nutify
    privileged: true
    cap_add:
      - SYS_ADMIN
      - SYS_RAWIO
      - MKNOD
    devices:
      - /dev/bus/usb:/dev/bus/usb:rwm
    device_cgroup_rules:
      - 'c 189:* rwm'
    volumes:
      - ./Nutify/logs:/app/nutify/logs
      - ./Nutify/instance:/app/nutify/instance
      - ./Nutify/ssl:/app/ssl
      - ./Nutify/etc/nut:/etc/nut
      - /dev:/dev:rw              # Full /dev access improves hotplug handling
      - /run/udev:/run/udev:ro    # Access to udev events
    environment:
      # ===== SERVER CONFIGURATION =====
      - SERVER_PORT=5050
      - SERVER_HOST=0.0.0.0
      # ===== LOGGING CONFIGURATION =====
      - LOG=true
      - LOG_LEVEL=DEBUG
      - LOG_WERKZEUG=true
      - ENABLE_LOG_STARTUP=Y
      - SSL_ENABLED=false
      - SECRET_KEY=test1234567890 # for password encryption and decryption in the database
      - UDEV=1                    # Improve USB detection
    ports:
      - 3493:3493
      - 5050:5050
      - 443:443
    restart: always
    user: root

⚠️ Reminder:
This is a TEST version, please run it separately from your main installation to avoid compromising your data.

👉 Stop your current Nutify instance before starting this one.

🧪 Please test all sections thoroughly, not just the new features!

🐞 If you find any bugs, report them in the BUG section, not here.

I'd like to keep this thread clean for TEST release announcements only.

🙏 Thanks everyone for your time and help!

[NEXUSBE]

Nice work

[mregni]

Works good for me, thanks!

[DartSteven]

image: dartsteven/test:amd64-0.1.6RC02 Ready to test (Fixed graphs and driver missing)

[DartSteven]

dartsteven/test:amd64-0.1.7.5TEST
I’ve added a login section (admin in the options) where you can create users and control which pages and settings they can access. I strongly recommend making a backup of your database—ideally, start with a fresh instance. It works both with an existing database and during the NUT configuration phase to create the admin account.

Like the previous beta, this version already includes the latest NUT 2.8.3 release.

Please let me know if it works for you and if you find any bugs.

[xhemp]

Just tested and it works fine, great job! Only thing is that because I have 2 separate UPSs, I run 2 Nutify instances, one on port 5050 and other on 5051. If I login or logout from any of them, it will log in/out on the other too, not a big deal really but just wanted to let you know.

[marlop352]

Hi, I need to be able to configure nutify via the docker-compose or an API, otherwise I can't integrate the deployment of it with my automations.
Right now the deployment and configuration of everything I have in running inmy homelab is automated,
I was considering Nutify to replace webnut (and add useful features) but having to manually reconfigure it any time I need to re-create the machine it's running on would be a royal pain, specially since I may just forget that I need to do that as nothing else needs it.

An API, environment variables or config files would all work fine, even an SQL imported to an external PostgreSQL database would work but that would be a tad annoying and need too many extra safety checks 😅

No need for all the options to be available this way (although that would be extra nice), just what is configured using the setup wizard (including the "Manual Nominal Power" setting).