[GH-ISSUE #42] contributing to the project ? #32

Open
opened 2026-03-02 15:47:22 +03:00 by kerem · 5 comments
Owner

Originally created by @aderumier on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/42

Hi,

I'm a proxmox contributor and I just found your nice project. I was working on a similar python project on my side (python/fastpi/asyncio) to fill the gap of missing features of pdm (I really can't code in rust ^_^), but I see than your project is more advanced, and I would like to help/contribute as your project is GPL.

one question: any reason to listen websocket on a different port ? is it a flask limitation to handle websocket upgrade ? (I have managed it easily on my side with fastapi+asyncio).
I really need this for security reason, I think I could workaround with a nginx or haproxy reverse proxy in front, but I think that the wss port sent to vnc client is hardcoded currently ?

Other things I have begin to work on my side:

  • cross cluster storage replication for disaster recovery (I have a lot of customer requesting about it, at least with zfs->zfs or ceph->ceph). -
  • central backup scheduling
  • oidc authen
  • user self service portal with quota by user (total vm cpu/total vm memory,.... )

I don't known if you have theses kind of features on your roadmap and if contributions are welcome ?

Originally created by @aderumier on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/42 Hi, I'm a proxmox contributor and I just found your nice project. I was working on a similar python project on my side (python/fastpi/asyncio) to fill the gap of missing features of pdm (I really can't code in rust ^_^), but I see than your project is more advanced, and I would like to help/contribute as your project is GPL. one question: any reason to listen websocket on a different port ? is it a flask limitation to handle websocket upgrade ? (I have managed it easily on my side with fastapi+asyncio). I really need this for security reason, I think I could workaround with a nginx or haproxy reverse proxy in front, but I think that the wss port sent to vnc client is hardcoded currently ? Other things I have begin to work on my side: - cross cluster storage replication for disaster recovery (I have a lot of customer requesting about it, at least with zfs->zfs or ceph->ceph). - - central backup scheduling - oidc authen - user self service portal with quota by user (total vm cpu/total vm memory,.... ) I don't known if you have theses kind of features on your roadmap and if contributions are welcome ?
Author
Owner

@aderumier commented on GitHub (Feb 10, 2026):

reverse proxy support for vnc/ssh websocket : https://github.com/PegaProx/project-pegaprox/pull/43

<!-- gh-comment-id:3876469248 --> @aderumier commented on GitHub (Feb 10, 2026): reverse proxy support for vnc/ssh websocket : https://github.com/PegaProx/project-pegaprox/pull/43
Author
Owner

@mkellermann97 commented on GitHub (Feb 10, 2026):

Hi @aderumier ,

Contributions are always welcome! Just a heads-up – we test all pull requests before merging, which can take up to two days.

Regards,
Marcus

<!-- gh-comment-id:3876545478 --> @mkellermann97 commented on GitHub (Feb 10, 2026): Hi @aderumier , Contributions are always welcome! Just a heads-up – we test all pull requests before merging, which can take up to two days. Regards, Marcus
Author
Owner

@MrMasterbay commented on GitHub (Feb 11, 2026):

Heyha @aderumier ,

just as further information thank you very much for the contributions! We've tested it in our LAB and will merge it with the next release :) . I hope thats fine for you? :)

Best regards,
Nico

<!-- gh-comment-id:3887722972 --> @MrMasterbay commented on GitHub (Feb 11, 2026): Heyha @aderumier , just as further information thank you very much for the contributions! We've tested it in our LAB and will merge it with the next release :) . I hope thats fine for you? :) Best regards, Nico
Author
Owner

@aderumier commented on GitHub (Feb 12, 2026):

Heyha @aderumier ,

just as further information thank you very much for the contributions! We've tested it in our LAB and will merge it with the next release :) . I hope thats fine for you? :)

Best regards, Nico

yes sure, no problem, no rush, thanks !

It was just small patches for start, I'll try to do more patch next week.

I'm still discovering the UI. I'll try to look to add French translation, as I'm from Belgium/France.

and maybe look for quota by tenant, as it shouldn't be too difficult to implement.

<!-- gh-comment-id:3888879635 --> @aderumier commented on GitHub (Feb 12, 2026): > Heyha [@aderumier](https://github.com/aderumier) , > > just as further information thank you very much for the contributions! We've tested it in our LAB and will merge it with the next release :) . I hope thats fine for you? :) > > Best regards, Nico yes sure, no problem, no rush, thanks ! It was just small patches for start, I'll try to do more patch next week. I'm still discovering the UI. I'll try to look to add French translation, as I'm from Belgium/France. and maybe look for quota by tenant, as it shouldn't be too difficult to implement.
Author
Owner

@IMNotMax commented on GitHub (Feb 24, 2026):

Hi, not a developper but I'm French (from France) and I live in Canada. I can help with French translation. My pleasure to help !

<!-- gh-comment-id:3948723467 --> @IMNotMax commented on GitHub (Feb 24, 2026): Hi, not a developper but I'm French (from France) and I live in Canada. I can help with French translation. My pleasure to help !
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/project-pegaprox-PegaProx#32
No description provided.