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

When a client node already exists entry should not be updated by install #223

Closed
peterschen opened this Issue Jun 1, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@peterschen
Contributor

peterschen commented Jun 1, 2015

I have a configured node working with facileManager. When I run php dns.php install my settings for that node are overriden (root directory, cache directory, ...) even though they haven't changed. I would expect that the node in facileManager is not updated when a matching entry (with the same serial) was found.

@peterschen

This comment has been minimized.

Contributor

peterschen commented Jun 1, 2015

If the default behavior is to update the configuration a way to specify the configuration in the client (e.g. as a define in config.inc.php) would be great. This is actually one of the last things which prevent an automatic deployment of clients.

@WillyXJ WillyXJ changed the title from When a DNS node already exists entry should not be updated by install to When a client node already exists entry should not be updated by install Jun 1, 2015

@WillyXJ WillyXJ added this to the 2.x release milestone Aug 21, 2015

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Aug 21, 2015

Added a client install option of 'no-update' to prevent the client from updating the database. This will go out with the next 2.x release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment