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
{{ message }}
This repository has been archived by the owner on Dec 19, 2019. It is now read-only.
Hi,
thanks for this great haproxyctl tool. In my use case, I have multiple haproxy instances on the same loadbalancer. The config files are split into generic parts end specific parts per instance. This modular approach is more scaleable and we can edit only 1 generic configpart which is used on all instances in just one file. As far as I can see, it is not possible to point haproxyctl to for example N configfiles of haproxy instance X without changing the ruby code. Do you have plans to support multiple haproxy instances and multiple configfiles in the future?
Kind regards,
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
thanks for this great haproxyctl tool. In my use case, I have multiple haproxy instances on the same loadbalancer. The config files are split into generic parts end specific parts per instance. This modular approach is more scaleable and we can edit only 1 generic configpart which is used on all instances in just one file. As far as I can see, it is not possible to point haproxyctl to for example N configfiles of haproxy instance X without changing the ruby code. Do you have plans to support multiple haproxy instances and multiple configfiles in the future?
Kind regards,
The text was updated successfully, but these errors were encountered: