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
Context
I want video clips accessible on a remote server (so that thief cloud not carry away the footage inside of a local server) but I can not get the bandwidth to stream multiple cameras to a remote server. So I need a local server that all cameras can stream to. This may be a common problem.
Architecture suggestions:
Worker/viewer
It would be ideal to have the ability to host UI/storage container on remote server and worker container working locally that would do all the recondition/processing. The two could communicate over network and worker would push clips to the remote server or connect to local streams when user would try to access them. Considering recent addition of go2rtc in current betas this separation should be less work than it may seam at first.
Federation
Another way could be is just adding a permission for other frigate server to view this ones streams/clips and upload them to it. This would require more processing resources over all but may be easier to implement.
Current solutions?
Also to the people who are storing clips/footage on remote server, from their local machine: What are you configs? Just a mount of remote storage? resync to manage the bandwidth? What has worked reliably for you?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Context
I want video clips accessible on a remote server (so that thief cloud not carry away the footage inside of a local server) but I can not get the bandwidth to stream multiple cameras to a remote server. So I need a local server that all cameras can stream to. This may be a common problem.
Architecture suggestions:
Worker/viewer
It would be ideal to have the ability to host UI/storage container on remote server and worker container working locally that would do all the recondition/processing. The two could communicate over network and worker would push clips to the remote server or connect to local streams when user would try to access them. Considering recent addition of go2rtc in current betas this separation should be less work than it may seam at first.
Federation
Another way could be is just adding a permission for other frigate server to view this ones streams/clips and upload them to it. This would require more processing resources over all but may be easier to implement.
Current solutions?
Also to the people who are storing clips/footage on remote server, from their local machine: What are you configs? Just a mount of remote storage? resync to manage the bandwidth? What has worked reliably for you?
Beta Was this translation helpful? Give feedback.
All reactions