13 Commits (dc2cb43f43d1feab965b3bcab579c430223e90ec)

Author	SHA1	Message	Date
Victor Seva	7d422b7878	MT#8763 check for .git before running the services ... On a multi directory config, the services depends on git. Check first if the git repository exists and warn about it Change-Id: I52e335c85ecf4a330da44b3088725623f3c04531	12 years ago
Victor Seva	5ed308c1a0	MT#8763 allow multiple config directories on templates not only "/etc" ... Change-Id: I1c8fc5fd45a0c34ba7542ddc6ce24793bd568cb5	12 years ago
Victor Seva	d9e6ba263d	MT#8067 check nodename no hostname to exclude ourselves	12 years ago
Michael Prokop	def862dd8a	MT#2231 status option: check for pull/push + check state of remote host(s)	12 years ago
Michael Prokop	fc5af3bbb2	MT#7577 services: check for newly added config files ... `git diff-index --name-only HEAD` was used because it was the only reasonable way to check for modified files back in Git 1.5. Sadly this command can't detect files that didn't exist inside the Git repository at all yet (so if a file was generated for the very first time the according services script wasn't executed necessarily). Instead nowadays we can rely on `git status --porcelain`, which wasn't available in Git 1.5 back then yet. Even in Debian/squeeze there's Git version 1.7.2.5-3 available, so it's save to depend on it. Updated Git package dependency accordingly, also switch from transitional git-core package to the actual git one. Tested-by: Alexander Lutay <alutay@sipwise.com>	12 years ago
Alexander Lutay	e3eda0cb3b	MT#5027 Speed up 'build' runs by using Perl daemon	12 years ago
Alexander Lutay	9206aa868a	Revert "MT#4141 Speed up 'build' runs by loading YAML files only once" ... This reverts commit 335d53c95c.	12 years ago
Kirill Solomko	ec2fa4eb1a	MT#4585 - added "--no-db-sync" option that skips sync-db/sync-constants	13 years ago
Michael Prokop	335d53c95c	MT#4141 Speed up 'build' runs by loading YAML files only once ... When runnning 'ngcpcfg build' (which is also executed when running 'ngcpcfg apply') we waste quite some time with loading the same YAML configuration files and merging them again and again. In a 'ngcpcfg build' run we don't have to re-load and merge those configuration files again and again (since they won't modify during a single run), instead just load+merge them *once* and re-use the result on all the following execution steps in the same run. Original: | # time ngcpcfg apply >/dev/null | ngcpcfg apply > /dev/null 149.01s user 9.49s system 96% cpu 2:43.57 total Reworked optimized runs: | # time ngcpcfg apply >/dev/null | ngcpcfg apply > /dev/null 81.25s user 8.62s system 95% cpu 1:34.17 total For debugging purposes you can execute 'ngcpcfg build' under NO_REUSE=1 to not use this feature, executing it under 'DEBUG=1' won't remove the so called reuse file which stores the merged configuration data. Thanks: Alexander Lutay for the initial patch and idea	13 years ago
Michael Prokop	f2e9a5e8e6	MT#4295 Be more strict with option handling when passing file names to grep	13 years ago
Michael Prokop	928cd68cf2	Simplify default configuration code	13 years ago
Michael Prokop	c3e1cb68d4	support additional configuration yml files via configuration directory ... Files in configuration directory EXTRA_CONFIG_DIR (being /etc/ngcp-config/config.d/ by default) with the suffix yml (so e.g. a file named pbx.yml can be shipped by an external Debian package) are additionally taken into consideration as main configuration files. Those extra configuration file(s) have higher precedence than the other yml configuration files (config.yml, network.yml,...), *except* for constants.yml which has the power to override all settings, including the ones from files inside EXTRA_CONFIG_DIR. Closes: sipwise-#3059	13 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago