Is there a better way to do this with whats included in freepbx or commercial modules? I was thinking just putting the script in cron and just have it run every so many hours. Then eventually making a form to add or modify the data.
What I would do is update your ivr3 to include the id and name from ivr_details and think of those as the unique key. Or add them to a separate cross reference table, however you want to handle it.
Then add logic to your system to fail and notify if there is a mismatch (aka someone changed it in FreePBX).
There is no way to do this in FreePBX itself.
Once you change the database, you will have to reload everything.
You can issue the fwconsole reload command from your script. That is the same as clicking the red "Apply Config" button.
I think that this decision has to come down to... is this a career change that you want? If this is what you WANT to do, then it is a huge opportunity to build your resume and experience. If this is not something that you want, this could suck big time. it's more about you and your goals than about career options.
That's why we set any WAN-fancing SSH port to something obscenely high like 41022, not for "security" but because of the logs. In fact, all of our sshd services run following that pattern, as does our internal HTTP(S) servers but the load balancers take in 80/443.
This prevents as many services as possible from running as root, which anything running port < 1024 does. I don't think most people even know this. At the very least if there's a NAT in play, one can always set ssh and web services ports much higher and just translate the ports to avoid the same issue.
(I know there are some work arounds like setcap on Linux, but in general this is the default behaviour on most machines)
For some reason this made me think of The Venture Bros, Hunter Gather says:
And we want your sad ass undercover agents to stop trying to infiltrate our group. Frankly we're tired of killing them and we can't afford the body bags!
I agree with Nick and Scott - while this is not good, it's definitely not as bad as it sounds... the bad thing - non technical people won't understand why and they'll just crucify LastPass instead.
I'll include myself as non technical person here. It does further put me off hosted solutions. That's not the only reason I use on-premise (Keepass) as I didn't really like LastPass when I tried it anyway. I do store my Keepass databases in the cloud though, but that's a different risk.
The sad fact of the matter is that unless you completely unplug yourself, you just can't avoid hosted solutions. I say sad, and others will say, what makes it sad? Life has so many advantages today because of the hosted/integrated solutions - this is a conundrum I haven't reconciled yet.