Export command-tree config data to rpt.conf syntax

[joshproehl]

Can we just dump it into custom/rpt.conf and have it parsed in the correct stanzas? Edit the rpt.conf file and add our own custom include of allstarhelper_phonetree.conf?

[ldaponte]

Of I understand the question, I would keep the processing task as quick as possible and only speak pre processed audio and not try to process the web calls and TTS during a touch tone request for a report. If you're talking about matching a touch tone request to a particular audio response then that is probably doable with some sort of lookup but I doubt there are that many different combinations needed. Your thoughts,

[joshproehl]

Here's the workflow I was imagining:

• The app should be run periodically (5 minutes) by cron. This run simply downloads data for each item in the conf file, creates the output TXT file, and runs it through TTS. Simple and fast. (I'm currently finding/building the best way to use the flite (festival-lite) engine to output our text as voice files)
• The app can be run manually using the --update-rpt-conf flag which will read our configuration JSON file and output either simply text defining the rpt.conf stanzas needed, or write it to a conf file. This should be run manually whenever you update the configuration JSON file.

I also want the app to be able to be run manually with a --generate-static flag which will generate a welcome-to-node message and any other static pieces of text we need TTS'd. Ideally all text read by the node should use the same voice. Suppose I should create an ER for that...

[ldaponte]

I hadn't noticed the code when I posted this. Makes sense - I get the auto configuration. If rpt.conf keeps processing, maybe we don't need to generate any config and instead just pass the DTMF received and if there is a match in the config then play the file so only one entry in rpt.conf needed - all speculation on my part since I'm still learning how apr_rpt works.

BTW, did some reading up on GO, what tools do you use? Is there a debugger or do I need to rely on logging only? Is there an IDE that understands go syntax?

[ldaponte]

This is an interesting line

apiResult := WXUGRes{}

JSON deserialized into an object that easily?

[ldaponte]

Just replied in the repo

-Larry

On 02.12.2015, at 18:56, Josh Proehl notifications@github.com wrote:

Here's the workflow I was imagining:

The app should be run periodically (5 minutes) by cron. This run simply downloads data for each item in the conf file, creates the output TXT file, and runs it through TTS. Simple and fast. (I'm currently finding/building the best way to use the flite (festival-lite) engine to output our text as voice files)
The app can be run manually using the --update-rpt-conf flag which will read our configuration JSON file and output either simply text defining the rpt.conf stanzas needed, or write it to a conf file. This should be run manually whenever you update the configuration JSON file.
I also want the app to be able to be run manually with a --generate-static flag which will generate a welcome-to-node message and any other static pieces of text we need TTS'd. Ideally all text read by the node should use the same voice. Suppose I should create an ER for that...

—
Reply to this email directly or view it on GitHub.

[joshproehl]

jsonErr := json.NewDecoder(resp.Body).Decode(&apiResult)

Is actually the line that takes the JSON file and parses the data into the empty apiResult struct we created, but yeah, it's just that easy! The structs at the top define what the JSON objects look like, using the json:"key_name" syntax to decide which key matches to which value. You'll notice that we don't have to define ALL the values either, just the ones we care about!

BTW, did some reading up on GO, what tools do you use? Is there a debugger or do I need to rely on logging only? Is there an IDE that understands go syntax?

I use vim/gvim as my editor. It does have go syntax highlighting, although I believe I use a plugin to offer some additional help. go build is all you need to compile it. (Although you'll need to go get once to make sure deps are downloaded.) I haven't actually done much with a debugger in go yet, but I've heard of Delve, as well as using GDB.

[joshproehl]

Stubbed in f1f07e7

The allstar node is currently down due to power outage so I can't test the syntax, but I wanted to write up the stub at least.