Web interface as a proper detached web application #338

New Issue

2026-10-05T04:14:02+02:00

adam commented

2026-10-05 04:14:02 +02:00

Currently, the web administration module is highly integrated into ZNC core. In fact, it is written in C++. This is somewhat awkward. So why not rewrite it as a proper web application (WSGI, Ruby, Java, whatever) and let the HTTP job for actual HTTP servers at the choice of the user? No problem leaving the basic standalone server for simple setups though. This is more a just for registering, unpretentious suggestion than a complaint.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Currently, the web administration module is highly integrated into ZNC core. In fact, it is written in C++. This is somewhat awkward. So why not rewrite it as a proper web application (WSGI, Ruby, Java, whatever) and let the HTTP job for actual HTTP servers at the choice of the user? No problem leaving the basic standalone server for simple setups though. This is more a just for registering, unpretentious suggestion than a complaint. ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2542706-web-interface-as-a-proper-detached-web-application?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:14:03 +02:00

Would this make webadmin to use different port than IRC clients use to connect to ZNC? I think that this is a bad thing as some people are running ZNC's on shells where they must ask for every port they need to be opened and there can be limitations in amounts of ports.

If registration was added to webadmin, it should be opt-in, not opt-out or forced option as there are people who aren't willing to open their ZNC's for random people.

Would this make webadmin to use different port than IRC clients use to connect to ZNC? I think that this is a bad thing as some people are running ZNC's on shells where they must ask for every port they need to be opened and there can be limitations in amounts of ports. If registration was added to webadmin, it should be opt-in, not opt-out or forced option as there are people who aren't willing to open their ZNC's for random people.

adam commented

2026-10-05 04:14:04 +02:00

The embedded server should handle this case (I think it should not be much complex to write a basic HTTP container for the brand new web application). So if users want, they can just continue using ZNC as they are used to, or they can switch to more flexible approach with proper HTTP servers. Additionally, the web application could even handle IRC through HTTP, who knows.

The embedded server should handle this case (I think it should not be much complex to write a basic HTTP container for the brand new web application). So if users want, they can just continue using ZNC as they are used to, or they can switch to more flexible approach with proper HTTP servers. Additionally, the web application could even handle IRC through HTTP, who knows.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#338