You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what you are trying to accomplish and why in non technical terms
I want to be able to have the config jsonschema definition available via a public URL so that I can validate config files without access to a running frigate deployment.
Describe the solution you'd like
Dump the config file jsonschema definition as part of the release pipeline and add it to release artifacts.
Describe alternatives you've considered
Exporting the jsonschema definition manually for each release
Starting a local frigate container every time I want to edit the configuration
Adding the schema definition to this repo
All of the above seem unnecessary complex or require duplicated work
Additional context
Currently the setup requires a running deployment of frigate, which is especially inconvenient if you are trying to debug a broken config file which results in frigate not starting.
The text was updated successfully, but these errors were encountered:
Describe what you are trying to accomplish and why in non technical terms
I want to be able to have the config jsonschema definition available via a public URL so that I can validate config files without access to a running frigate deployment.
Describe the solution you'd like
Dump the config file jsonschema definition as part of the release pipeline and add it to release artifacts.
Describe alternatives you've considered
All of the above seem unnecessary complex or require duplicated work
Additional context
Currently the setup requires a running deployment of frigate, which is especially inconvenient if you are trying to debug a broken config file which results in frigate not starting.
The text was updated successfully, but these errors were encountered: