You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ProxLB evolved from a very small tool with a very limited functionality. This came, because after publishing ProxLB many feature requests came in and were solved and integrated in probably not the best ways which resulted in some dirty ways and not that good maintainable code. While it's still written in a good way, this can be improved a lot which also makes all the things around it easier. It should also move from configparser to yaml to avoid unnecessary type converts and makes it easier to handle the input data. In the past, also often some questions came up, how to treat values even they were documented and using them directly in the according way makes it more clear.
This will also change the way how ProxLB should be used. In the past, there were several ideas like a single management host or container, installed on one or many Proxmox hosts. With the upcoming version, it will be treated as a fully managed appliance and should only run on a single host which orchestrates everything. This also ensures that the overall handling becomes easier, doesn't require any synchronization between the nodes (e.g. locking) and provides a way for a new UI integration.
Details
This will include a bigger change and also switching from a ini alike config to a yaml config file.
The text was updated successfully, but these errors were encountered:
General
ProxLB evolved from a very small tool with a very limited functionality. This came, because after publishing ProxLB many feature requests came in and were solved and integrated in probably not the best ways which resulted in some dirty ways and not that good maintainable code. While it's still written in a good way, this can be improved a lot which also makes all the things around it easier. It should also move from configparser to yaml to avoid unnecessary type converts and makes it easier to handle the input data. In the past, also often some questions came up, how to treat values even they were documented and using them directly in the according way makes it more clear.
This will also change the way how ProxLB should be used. In the past, there were several ideas like a single management host or container, installed on one or many Proxmox hosts. With the upcoming version, it will be treated as a fully managed appliance and should only run on a single host which orchestrates everything. This also ensures that the overall handling becomes easier, doesn't require any synchronization between the nodes (e.g. locking) and provides a way for a new UI integration.
Details
This will include a bigger change and also switching from a ini alike config to a yaml config file.
The text was updated successfully, but these errors were encountered: