swiftugandan

This could be the issue with the file: https://stackoverflow.com/questions/34118013/how-to-determine-webm-duration-using-ffprobe The format `matroska,webm` is not known by mediacms, and the file also lacks a `duration` ``` { "format": { "filename": "/files/liveMeetingrecord6.webm",...

Running on a raspberry-pi then possible, but without the transcoding processes. See here - https://github.com/mediacms-io/mediacms/discussions/285 to disable transcoding. @simao-silva please share your raspberry pi build instructions if you don't mind.

Good first issue for anyone wanting to contribute, https://github.com/mediacms-io/mediacms/blob/87539eb8efb58fa2d0b200d5016c9b6b6ca5d642/users/forms.py#L32 @mgogoulos What max size should we allow?

I am in the process of creating a docker-compose file based on the design below: This design should act as a basis for a scaleable deployment in docker, kubernetes or...

I think changing volumes in the migrations container (in the docker-compose-named-volimes.yaml) to - https://github.com/mediacms-io/mediacms/blob/fb0f3ee739dfc2951b593842951e1883f6664f46/docker-compose-named-volumes.yaml#L30 Should fix the issue

+1

@mgogoulos Just wondering, doesn't this need the frontend/react code?

@MikeyYeahYeah please feel free to pick up any of the tasks, would be nice to have a docker deployment peer to bounce ideas off ;)

> @swiftugandan thank you for your contribution and efforts with this, but I am going to close this pull request as I think it needs more thought and maybe in...

Perhaps you should consider looking at other `fs.*` calls and update them to use `fs.promises`, not just the user api end-point