Reference Issues
#395
Summary
Feature request
Please add a bulk edit action for Hosts, especially for Advanced Options.
Current problem:
When an admin has many hosts, changing the same option for all of them is very time-consuming. For example, changing the uTLS / client fingerprint from chrome to firefox requires editing each host manually.
Suggested solution
Add a bulk action in the Hosts page:
- Select multiple hosts
- Click "Bulk edit"
- Choose one or more fields to update
- Apply changes to all selected hosts
Useful fields for bulk editing:
- fingerprint / uTLS fingerprint
- SNI
- ALPN
- allowInsecure
- security / flow
- port
- path
- host-related Advanced Options
Why it is useful
This would make host management much easier for installations with many hosts. It would also reduce configuration mistakes when the same option needs to be changed across many hosts.
Example use case
I have 29 hosts and need to change the fingerprint from chrome to firefox. Currently this requires opening and editing every host one by one.
Basic Example
Example workflow:
- Open the Hosts page
- Select several hosts using checkboxes
- Click "Bulk edit"
- Choose the fields to update
- Set
fingerprint to firefox
- Apply changes to all selected hosts
Example use case:
An admin has 29 hosts and wants to change the fingerprint from chrome to firefox. With the current UI, every host has to be edited one by one. With bulk editing, the admin could select all required hosts and apply the new fingerprint in one action.
Fields that would be useful for bulk editing:
- fingerprint / uTLS fingerprint
- SNI
- ALPN
- allowInsecure
- security / flow
- port
- path
- other host Advanced Options
Drawbacks
The main drawback is that bulk editing can accidentally change many hosts at once if used incorrectly.
To reduce this risk, the UI could show a confirmation dialog before applying changes, for example:
"You are about to update 29 hosts. This action will change the selected fields for all selected hosts."
It may also be better to update only explicitly selected fields, so empty fields do not overwrite existing host settings by mistake.
Unresolved questions
A few implementation details may need to be decided:
- Should bulk editing be available only for Advanced Options, or for all host fields?
- Should the UI allow editing multiple fields at once, or only one field per bulk action?
- Should there be a confirmation preview showing which hosts and fields will be changed?
- Should this feature be limited to admins with specific permissions?
Reference Issues
#395
Summary
Feature request
Please add a bulk edit action for Hosts, especially for Advanced Options.
Current problem:
When an admin has many hosts, changing the same option for all of them is very time-consuming. For example, changing the uTLS / client fingerprint from
chrometofirefoxrequires editing each host manually.Suggested solution
Add a bulk action in the Hosts page:
Useful fields for bulk editing:
Why it is useful
This would make host management much easier for installations with many hosts. It would also reduce configuration mistakes when the same option needs to be changed across many hosts.
Example use case
I have 29 hosts and need to change the fingerprint from
chrometofirefox. Currently this requires opening and editing every host one by one.Basic Example
Example workflow:
fingerprinttofirefoxExample use case:
An admin has 29 hosts and wants to change the fingerprint from
chrometofirefox. With the current UI, every host has to be edited one by one. With bulk editing, the admin could select all required hosts and apply the new fingerprint in one action.Fields that would be useful for bulk editing:
Drawbacks
The main drawback is that bulk editing can accidentally change many hosts at once if used incorrectly.
To reduce this risk, the UI could show a confirmation dialog before applying changes, for example:
"You are about to update 29 hosts. This action will change the selected fields for all selected hosts."
It may also be better to update only explicitly selected fields, so empty fields do not overwrite existing host settings by mistake.
Unresolved questions
A few implementation details may need to be decided: