microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Confusing configuration instructions on AksSamples/teams-recording-bot

Open
#439 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
Regarding the configuration for local debugging with ngrok.

The host.sh script is supposed generate a certificate for contoso.ngrok.io.

In the instructions in the .env file there is a setting AzureSettings__ServiceDnsName=contoso.ngrok.io that is then used to setup the MediaPlatformSettings field ServiceFqdn.

But how can this domain for which we generated a certificate then point at 1.tcp.ngrok.io:PORT?

It is not clear to me how can all this be accomplished without a custom domain and a CNAME entry, which would be quite handy, as explained in the other bot documentation (e.g. HueBot).

Are the instructions wrong or am I missing something?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the teams-recording-bot instructions, its .env configuration, and the host.sh script mentioned in the issue. Compare the local-debugging setup with the linked HueBot documentation, then verify whether the certificate and ngrok endpoint instructions are consistent. Done means the sample documents a clear, working configuration or identifies the required correction.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.