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

Be able to edit a non working config within Frigate without having to edit the config externally before then restarting Frigate #11893

Open
Londonlad95 opened this issue Jun 11, 2024 · 4 comments
Labels
enhancement New feature or request pinned

Comments

@Londonlad95
Copy link

Describe what you are trying to accomplish and why in non technical terms

I want to be able to log in to Frigate and edit the config if it's not working so that I don't have to go and search up the correct folder through a command line for example and manually edit the config file before then restarting Frigate.

Describe the solution you'd like

I want Frigate to start, and if the config doesn't work, at least get you into the Frigate config editor via the Container IP so config changes can much more easily be sorted remotely and quickly.

Describe alternatives you've considered

Not sure there are any alternatives? If there are, then please let me know.

@Londonlad95 Londonlad95 added the enhancement New feature or request label Jun 11, 2024
@nomonkeynodeal
Copy link

I asked for this already. They apparently want to keep Frigate limited to an elite club of people who know how to find configs on a Linux system buried within several containers.

@NickM-27
Copy link
Sponsor Collaborator

this feature request has been pinned which means it will be implemented in a future version, there is no need for speculation

@nomonkeynodeal
Copy link

this feature request has been pinned which means it will be implemented in a future version, there is no need for speculation

I was instantly shut down when I suggested the same thing a few weeks ago, but whatever. I'm glad to hear it. This is probably more important to Frigate's growth than devs realize.

@digiltd
Copy link

digiltd commented Jun 22, 2024

I asked for this already. They apparently want to keep Frigate limited to an elite club of people who know how to find configs on a Linux system buried within several containers.

What I do when I forget where things are is use the history feature in the command line, so assuming you have typed nano ~/frigate/config/config.yml at least once when setting it up initially, when you next open a terminal and ssh into the computer running frigate, just press the up arrow key to step through previous commands you have used. Very handy when you want to retrace your steps.

Also a good idea generally to keep a little text file of notes when installing stuff like this, just copy and paste in anything you think you might need again. Like when everything is nice and stable, copy and paste your config into it so you can always jog your memory of that weird url you had to use to access the stream on a generic cheapy camera from amazon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned
Projects
None yet
Development

No branches or pull requests

4 participants