Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

populate d_mappings from conf file? #60

Closed
bechampion opened this issue Oct 5, 2021 · 3 comments
Closed

populate d_mappings from conf file? #60

bechampion opened this issue Oct 5, 2021 · 3 comments
Assignees

Comments

@bechampion
Copy link

Hi!
I can't find this in the github repo or in the code , but is there any way to load mappings and other configurations from a file?
I am looking at the code and it seems that the map vhost to backend is mainly being held in memory and load through the cli .

I personally need this to guarantee that on failure the apps comes back with the same conf (could be done with systemd hooks , but a config file would be nicer?)

Thank you for putting this on github , been waiting for something like this for quite a while.

@adamncasey
Copy link
Contributor

Hey @bechampion, thanks for the question.

There is no config file for amqpprox. The main reason for this the awkwardness around synchronising up front/static config with dynamic config updates.

As described in #58 - our setup is similar to how you describe, our start script for the proxy invokes amqpprox, and then also sends it all of the config known up front.

Does this answer your question?

@bechampion
Copy link
Author

Hey @adamncasey no worries, i will let systemd populate the config post start , and unblock with iptables once its al ready . thank you for this product!

@adamncasey
Copy link
Contributor

Unblocking with iptables seems fine, though I'm not sure if you noticed that you can also tell amqpprox to listen over the control socket too.

This way you can pass all of the configuration to amqpprox, then tell it to start listening. This is what we do - might simplify things a little?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants