Support for SSHFS

[Funtime60]

It seems that since the command is already executed via ssh, that using SSHFS or reverse SSHFS would make sense and maybe could even make the file transfer automatic and or more secure.

I'm writing this too late in the day(night) because I'm really eager to get started with this project tomorrow so I'll get back with more research in the morning.

Ultimately my goal is to have rffmpeg work completely automatically, maybe even chained so there'd be 1-2 control "servers" with rffmpeg pointing to a dozen targets. These "servers" would then be targets for other machines with actual jobs. These servers and actual targets could then be isolated to another network even.

[joshuaboniface]

If you mean SSHFS instead of NFS, as far as I know yes this will work fine.

[Funtime60]

I'm sorry it took me this long to reply. I was sleep deprived when I wrote this originally so I didn't get my idea across. Since rffmpeg requires ssh access, It seemed like if we could use an ssh based file system, it would allow for automated mounting. I realize now that SSHFS might not be the answer and that it'd require lots of work on rffmpeg's part, but I think that it'd be very nice if rffmpeg could parse the files involved in a command and then translate those locations to allow for a node to automatically reach the required files. Is this beyond the intended features? Another option would be to support it with an optional toggle so that an rffmpeg aware user could tell rffmpeg that the file/folder locations in the command are simpler so we don't need to fully parse all ffmpeg options. Thank you. Sincerely: Daniel Peaslee

…

On Mon, Oct 28, 2024 at 1:05 AM Joshua M. Boniface ***@***.***> wrote: If you mean SSHFS instead of NFS, as far as I know yes this will work fine. — Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF3U3U7M4PEST7PCIF6CORTZ5XO5FAVCNFSM6AAAAABQSQJSUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQG4YTEMZVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>