I propose a feature that allows users to define custom names for the Coreflux broker when installing it as a Windows service or daemon, enhancing the hubless installation experience.
Which component(s) is this request for?
[X] Coreflux Broker
[X] Coreflux Hub
[ ] Flux Assets
[ ] Flux Language
[ ] Power Ups
[ ] User Experience (UX)
[ ] Documentation
[ ] Conceptual Features
Is your feature request related to a problem? Please describe.
Implement an option during the installation process that prompts the user to enter a custom service name. This could be achieved through a small window asking for the name during the installation.
Describe the solution you'd like
I would like to see an enhancement in the installation process that includes a step for defining security protocols. This could involve setting up SSL/TLS encryption for all communication during the installation process and ensuring that all default passwords are changed to strong, user-defined passwords before the broker becomes operational.
Describe alternatives you've considered
This feature would provide greater flexibility and control to users, allowing them to maintain consistent naming conventions across services and avoid potential conflicts. It would also improve clarity when managing multiple broker instances, making it easier to identify and interact with each service.
Tell us about your request
I propose a feature that allows users to define custom names for the Coreflux broker when installing it as a Windows service or daemon, enhancing the hubless installation experience.
Which component(s) is this request for?
Is your feature request related to a problem? Please describe.
Implement an option during the installation process that prompts the user to enter a custom service name. This could be achieved through a small window asking for the name during the installation.
Describe the solution you'd like
I would like to see an enhancement in the installation process that includes a step for defining security protocols. This could involve setting up SSL/TLS encryption for all communication during the installation process and ensuring that all default passwords are changed to strong, user-defined passwords before the broker becomes operational.
Describe alternatives you've considered
This feature would provide greater flexibility and control to users, allowing them to maintain consistent naming conventions across services and avoid potential conflicts. It would also improve clarity when managing multiple broker instances, making it easier to identify and interact with each service.
Is this request for a new asset?
no
Additional context
No response