Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add a dedicated docu repro for PROXMOX: NetAlertX-PROXMOX

Open
#1,516 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose
Domain
documentation

Research direction

Read the linked NetAlertX-Unraid documentation example and the NetAlertX Docker Compose documentation first. The issue proposes a PROXMOX deployment guide using a Dockge LXC and notes that Debian 13 LXC work is ongoing, but does not specify a target file or exact scope. Done would be a dedicated, usable PROXMOX guide covering the deployment described.

Written by the indexing model from the issue text.

Description

Contributors 🙏 documentation 📚 help wanted 🆘 Waiting for reply⏳
Is there an existing issue for this?
  • I have searched the existing open and closed issues
What document or section does this relate to?

New Documentation repro for PROXMOX users: NetAlertX-PROXMOX

See as an example: https://github.com/netalertx/NetAlertX-unraid

Describe the issue

see above

Your suggestion or proposed solution

see above

What type of issue is this?
  • Missing information
  • Inaccurate or outdated information
  • Unclear or confusing content
  • Structure or organization improvements
  • Other (explain in issue)
Anything else?

Deployment of NetAlertX via a Dockge LXC.

Image

NetAlertX LXC on a Debian 13 based system

  • Ongoing
Can I help implement this? 👩‍💻👨‍💻
  • Yes, I’d like to help implement the improvement
  • No, I’m just suggesting the idea
Dominant language
Python
Stars
7.2k
Forks
456
Avg merge
17h 59m
Merged PRs (30d)
26

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from netalertx/NetAlertX

All issues in netalertx/NetAlertX

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.