Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RunOnInit #3214

Closed
10 tasks
dlucas9 opened this issue Apr 9, 2024 · 2 comments
Closed
10 tasks

RunOnInit #3214

dlucas9 opened this issue Apr 9, 2024 · 2 comments

Comments

@dlucas9
Copy link

dlucas9 commented Apr 9, 2024

Which version are you using?

v1.6.0

Which operating system are you using?

  • [ x] Linux amd64 standard
  • Linux amd64 Docker
  • [ x] Linux arm64 standard
  • [ x] Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

RunOnInit complains with
"ERR: a path with a regular expression (or path 'all') does not support option 'runOnInit'; use another path"

Describe how to replicate the issue

Set a command for RunOnInit as described in the README and run mediamtx.

Did you attach the server logs?

NO

Did you attach a network dump?

NO

@eravellaSC
Copy link

Did you set the RunOnInit for all path? You can't do that, as the error suggests.

@aler9
Copy link
Member

aler9 commented May 17, 2024

Hello, runOnInit is meant to be moved inside the paths section, in this way:

paths:
  mypath:
    runOnInit: mycommand

The documentation is definitely not clear, this is because all path parameters were recently moved to pathDefaults, which is a new variable that allows to set default values for all paths. There are some variables that cannot be set automatically on all paths but must be set on explicit paths. We'll see what we can do about it in the future.

@aler9 aler9 closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants