Update download link for Proxmox installer

[andrewbeaton]

Updated download link to point to new netalertx repository instead of older jokob-sk repository URL.

Summary by CodeRabbit

• Documentation
  • Updated the Proxmox installer download instructions to use the current NetAlertX repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 55ad744d-c998-42c2-bbcb-d412347a7480

📥 Commits

Reviewing files that changed from the base of the PR and between 1bbd1f1 and a724267.

📒 Files selected for processing (1)

• install/proxmox/README.md

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The Proxmox installer download command now points to the netalertx/NetAlertX GitHub repository. The subsequent execution and permission commands remain unchanged.

Changes

Proxmox installer update

Layer / File(s)	Summary
Update installer download source install/proxmox/README.md	The installer download URL changes from jokob-sk/NetAlertX to netalertx/NetAlertX.

Merge Risk: ⚪ Minimal · up to a7242

The installer documentation now points to the new repository location without changing execution or permission behavior; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the Proxmox installer download link.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Com177]

Can someone please elaborate on why this Proxmox LXC installer should be installed on a fresh server? What databases are affected? I want to simplify my installation. I've been running NetAlertX (v25.10.1) in Portainer on a Docker LXC in Proxmox and it runs fine but I'm running into memory issues.

As an FYI, my "local" drive is 70Gb and is rapidly filling with data. (see below) NetAlertX is the only container running in Docker and writes to volumes on this drive. I want to have NetAlertX directly on Proxmox but the warnings make it sound like it will interfere with my existing containers / VM. Maybe eventually the README.md can be updated to explain the dangers?

Many Thanks

[jokob-sk]

It's just preference. The Proxmox installer is only community supported though without official support.

Unsure what the above graph depicts as more context is needed. If you think it's an issue with the app, please open a separate issue and provide logs and more context.

[Com177]

OK, good to know. I hope it becomes mature enough to release it as an official LXC. That graph depicts the amount of data written by my docker instance of NetAlertX to my Proxmox "local" drive over the past year. The only container running in my docker is NetAlertX. I'm running the Legacy version of NetAlertX. Looks like I will run out of space in 1-3 months. The app otherwise runs fine by implementing macvlans to access all of my vlans.

I will submit a ticket to the Github repository and hopefully you'll know what's going on. I see data in Maintenance > Logs from: /app/log/app.log , /app/log/app_front.log and in /var/log/nginx/error.log. Which do you need and I will post a ticket with that information. If it's something else I will need the filename(s) and path(s).

Thanks!

[jokob-sk]

In one of the later versions I optimized log retention (I think this version https://github.com/netalertx/NetAlertX/releases/tag/v26.7.1), so depending on which files are causing the growth, the upgrade to a newer version might solve this. Usually /app/log/app.log are most helpful (if you follow the bug issue template it specifies which logs and what else to submit).

[Com177]

I'm running v 25.10.1; this version is before the major upgrade to the new directory system. Last question, can I install the latest version to docker and run them side by side or will that cause conflicts? I'm thinking if I can get the newest version working along side the older version I can then delete the older version and not bother trying to fix it. I know that an upgrade from the old version to the latest version will crash it. If not I will go to the repo and post publicly.

[jokob-sk]

yep, you can, just note:

spin up a separate container (make sure you use a unique PORT and GRAPHQL_PORT if running instances concurrently) with its own DB and config (a copy of your current setup),