support local storage path config

[shanjunmei]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I think the code supports storing locally, but there is no place to configure the local path. Can we open this configuration option? In fact, even if cloud storage is used, there is usually a simple way to use NFS to map cloud storage to local storage for direct access
Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[mpisat]

Egress supports writing to local path when you don't provide S3 or other options. you need to use full path in the egress request like /mnt/nfs/blabla/filename
and it will write there. make sure that folder is mounted with docker for self-hosted.
for cloud, why would livekit connect to your NFS when you can simply download these files from whatever S3, which doesn't require mounting, safe and secure. Get a cheap S3 provider, download files to your NFS, delete them, it won't cost much money considering you pay in hourly billing.

[jordiup]

@mpisat seeing the following error

❌ Failed to start audio egress: Bad Request: request has missing or **invalid field: output**
    at TwirpRpc.request (/Users/jordihermoso/code/agent-starter-node/node_modules/.pnpm/livekit-server-sdk@2.13.3/node_modules/livekit-server-sdk/dist/TwirpRPC.js:59:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async EgressClient.startRoomCompositeEgress (/Users/jordihermoso/code/agent-starter-node/node_modules/.pnpm/livekit-server-sdk@2.13.3/node_modules/livekit-server-sdk/src/EgressClient.ts:227:18)
    at async Timeout._onTimeout (/Users/jordihermoso/code/agent-starter-node/src/agent.ts:998:33) {
  status: 400,
  code: 'invalid_argument',
  metadata: undefined
}

when ran with

const localFilePath = `/out/${audioFilePath}`;

// For local storage, completely omit the output property
audioFileOutput = new EncodedFileOutput({
  fileType: EncodedFileType.MP4,
  filepath: localFilePath,
});

const audioEgressInfo = await egressClient.startRoomCompositeEgress(
  roomName,
  audioFileOutput,     // Pass the EncodedFileOutput directly
  { audioOnly: true }, // RoomCompositeOptions
);

i've mounted out in my docker file

running
lk agent deploy
then
pnpm dev

[mpisat]

Failed to start audio egress: Bad Request: request has missing or invalid field: output
you're using it wrong.
check out:
https://docs.livekit.io/home/egress/outputs/

req := &livekit.RoomCompositeEgressRequest{}
//req := &livekit.WebEgressRequest{}
//req := &livekit.ParticipantEgressRequest{}
//req := &livekit.TrackCompositeEgressRequest{}
req.FileOutputs = []*livekit.EncodedFileOutput{
  {
    Filepath: "myfile.mp4",
    Output: &livekit.EncodedFileOutput_S3{
      S3: &livekit.S3Upload{
        ...
      },
    },
  },
}

Output field is necessary (without S3 in your case)

[jordiup]

Damn, working hard on the weekend, appreciate the snappy response, give me a moment

[mpisat]

Damn, working hard on the weekend, appreciate the snappy response, give me a moment

I’m not part of livekit team but I appreciate their products. Giving back to open source community any way I can.

[biglittlebigben]

Did you manage to make this work?