--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#!substdef "!MY_AMQP_SECONDARY_URL!zone=z2;kazoo://guest:guest@z2_AMQP_IP:5672!g
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+unsubscribe@googlegroups.com.
The reason for not modifying default.cfg is then the next time an RPM is released with a new config, the RPM manager won’t overwrite default.cfg (which it SHOULD) because you’ve touched it.
We EXPECT local.cfg not to get overwritten when we strategize on where to put new feautres & such and try to keep that file backward compatible. We do NOT for the other files – we expect the other files not to be touched.
If you modify default.cfg then you have to make sure each time you upgrade that you maintain the differences between the shipped default.cfg and your modified one, the RPMs won’t do it for you. Hence why the recommendation is to use local.cfg
I’m also still checking on the discrepancy between my understanding of the requirement to use the zones and whatever is in 4.1 (I know 4.0 did not require this)
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+unsubscribe@googlegroups.com.