Feature request: clone network #986

New Issue

2026-10-05T04:57:08+02:00

adam commented

2026-10-05 04:57:08 +02:00

To keep all modules and channels configurations from an existing network, would be useful to have the clone network function.

Personal test to reproduce this:

Copy the configuration of network inside znc.conf
Change the network name.

The modules configurations for the created network require user intervention to set the required options (example: enabling sasl authentication).

To keep all modules and channels configurations from an existing network, would be useful to have the clone network function. Personal test to reproduce this: - Copy the configuration of network inside znc.conf - Change the network name. The modules configurations for the created network require user intervention to set the required options (example: enabling sasl authentication).

adam commented

2026-10-05 04:57:09 +02:00

From my time spent in #znc this seems to be a reasonable feature request. Perhaps it can be done via *controlpanel and/or webadmin, similar to cloneuser. I suggest that the command/process take (at least) 3 additional arguments besides target user and target network: new network name, and new server address and port (which would function to remove all previously-specified servers). Such as:
/msg *controlpanel clonenetwork <user> <oldnetworkname> <newnetworkname> irc.something.com +6697
If the new server address and port are optional, /msg *controlpanel clonenetwork <user> <oldnetworkname> <newnetworkname> [<server> <port>] then the previously-defined servers could remain unaffected.

From my time spent in #znc this seems to be a reasonable feature request. Perhaps it can be done via *controlpanel and/or webadmin, similar to cloneuser. I suggest that the command/process take (at least) 3 additional arguments besides target user and target network: new network name, and new server address and port (which would function to remove all previously-specified servers). Such as: `/msg *controlpanel clonenetwork <user> <oldnetworkname> <newnetworkname> irc.something.com +6697` If the new server address and port are optional, `/msg *controlpanel clonenetwork <user> <oldnetworkname> <newnetworkname> [<server> <port>]` then the previously-defined servers could remain unaffected.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#986