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
When "deleteHLSFilesOnEnded=true", HLS files (ts and m3u8) are duly deleted from the AntMedia server after the stream publishing is stopped. This doesn't happen when pushing such files on an S3 bucket with the "hlsHttpEndpoint=http://127.0.0.1:5080/LiveApp/hls-upload" option. If the user is not careful, this can lead to filling the bucket with thousands of files over time which is not desirable and can lead to costing issues as well.
The expectation is that, when setting "deleteHLSFilesOnEnded=true", HLS files are removed regardless whether the files are local or remote. As the server already deletes older ts files (because of the rotation) from the S3 bucket whilst the stream is being published, it has already the core functionality to remove remote files so the requested feature should be trivial to implement.
The text was updated successfully, but these errors were encountered:
When "deleteHLSFilesOnEnded=true", HLS files (ts and m3u8) are duly deleted from the AntMedia server after the stream publishing is stopped. This doesn't happen when pushing such files on an S3 bucket with the "hlsHttpEndpoint=http://127.0.0.1:5080/LiveApp/hls-upload" option. If the user is not careful, this can lead to filling the bucket with thousands of files over time which is not desirable and can lead to costing issues as well.
The expectation is that, when setting "deleteHLSFilesOnEnded=true", HLS files are removed regardless whether the files are local or remote. As the server already deletes older ts files (because of the rotation) from the S3 bucket whilst the stream is being published, it has already the core functionality to remove remote files so the requested feature should be trivial to implement.
The text was updated successfully, but these errors were encountered: