Connecting to go-vod with Unix sockets

[hkcomori]

Is your feature request related to a problem? Please describe.
I host Memories on a rental server, but the shared host does not allow me exclusive use of specific ports and does not allow me to use the transcoding feature by go-vod.

Describe the solution you'd like
It would be great if Memories could connect to go-vod via Unix sockets.

Describe alternatives you've considered
Hosting go-vod externally would be an alternative, but requires additional costs.

Additional context
Using Unix sockets was discussed in #354, but it is still not available because another approach solved the issue.
The discussion shows that Memories can connect via Unix sockets if it uses curl.
In addition, if add an option to go-vod that can listen to Unix sockets, this could be done.

[pulsejet]

From a technical standpoint this ought to be supported.

But I want to caveat that since transcoding is very very expensive, the shared server company will likely not be happy if you do this (you might violate some TOS)

[hkcomori]

Thank you, I will check the load on a small scale operation before deciding whether or not to enable it in a production instance.

By the way, the settings (Referenced here) I tried are below:

  'memories.exiftool.tmp' => '/home/username/.cache/nextcloud',
  'memories.vod.disable' => false,
  'memories.vod.ffmpeg' => '/home/username/.local/bin/ffmpeg',
  'memories.vod.ffprobe' => '/home/username/.local/bin/ffprobe',
  'memories.vod.tempdir' => '/home/username/.cache/go-vod',
  'memories.vod.bind' => '/home/username/.local/state/go-vod.sock',

I got the following error log (with Nextcloud Hub 9 (30.0.5) and Memories 7.4.1):

2025/02/12 09:13:48 Starting go-vod 0.2.5 on /home/username/.local/state/go-vod.sock
2025/02/12 09:13:48 Error starting server: listen tcp: address /home/username/.local/state/go-vod.sock: missing port in address