Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. MiroTalk
  3. MiroTalk SFU: Recording not possible?

MiroTalk SFU: Recording not possible?

Scheduled Pinned Locked Moved Unsolved MiroTalk
20 Posts 4 Posters 122 Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • MiroTalkM Offline
    MiroTalkM Offline
    MiroTalk
    wrote last edited by
    #11

    Ok from what understand: Cloudron allows writing only to /app/data, while /app/code is read-only, so all dynamic folders (rec, rtmp, uploads, etc.) must be moved into /app/data.

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote last edited by
      #12

      Thanks for all the insights here. So I think the folder to store recordings should then default to /app/data/rec or so with an option to configure that to use a different volume (not sure how large those recordings are)

      For RTMP_DIR is this some kind of temporary directory and thus maybe should be configured as /tmp/... or maybe even /run/... ?

      1 Reply Last reply
      0
      • MiroTalkM Offline
        MiroTalkM Offline
        MiroTalk
        wrote last edited by MiroTalk
        #13

        Yeah, setting the recordings directory RECORDING_DIR to /app/data/rec makes sense. This keeps all generated recordings inside the application’s persistent data area, which is consistent and easy to manage.

        Regarding RTMP_DIR, it is not a temporary directory.
        This directory is used to store the media files that will be streamed via RTMP. Since these files may need to remain available for repeated or scheduled streaming, it’s better to keep them in a persistent and organized location. Can be also in /app/data/rtmp as consistent with the rest of the project’s data layout.

        So in summary:

        • RECORDING_DIR → /app/data/rec
          Stores recordings generated by the application.

        • RTMP_DIR → /app/data/rtmp
          Stores video files intended for RTMP streaming, not temporary, should persist.

        1 Reply Last reply
        0
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote last edited by
          #14

          perfect, I will prepare a package update then. So just to double check, this only applies to the SFU flavor of mirotalk?

          1 Reply Last reply
          0
          • MiroTalkM Offline
            MiroTalkM Offline
            MiroTalk
            wrote last edited by
            #15

            perfect, I will prepare a package update then. So just to double check, this only applies to the SFU flavor of mirotalk?

            WIP on MiroTalk SFU: Let me fix this first, then I’ll ping you when done 🙂

            1 Reply Last reply
            1
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote last edited by
              #16

              in case your code would ensure the paths via "mkdirp()" it would make the package code easier 🙂

              1 Reply Last reply
              1
              • MiroTalkM Offline
                MiroTalkM Offline
                MiroTalk
                wrote last edited by MiroTalk
                #17

                @nebulon @James @shrey

                Implemented in MiroTalk SFU v2.0.14 — Docker image is building now (available in ~1 hour).

                • Commit
                • Build

                For Cloudron deployments, server-side recording should now work using the following configuration:

                Recording

                RECORDING_ENABLED=true
                RECORDING_DIR='../data/rec'            # Path relative to /app/code → resolves to /app/data/rec
                RECORDING_MAX_FILE_SIZE=1073741824     # Max file size in bytes (default: 1GB)
                

                RTMP

                RTMP_DIR='../data/rtmp'                # Path relative to /app/code → resolves to /app/data/rtmp
                

                Note

                If the target directories do not exist, MiroTalk SFU will automatically create them at runtime, just like before.

                Cloudron automatically mounts /app/data, so using ../data/... ensures the app writes to the persistent, writable directory.

                1 Reply Last reply
                6
                • nebulonN Offline
                  nebulonN Offline
                  nebulon
                  Staff
                  wrote last edited by
                  #18

                  New package is out. Thanks for all the work @mirotalk-57bab571 and being so proactive here!

                  MiroTalkM 1 Reply Last reply
                  4
                  • nebulonN nebulon

                    New package is out. Thanks for all the work @mirotalk-57bab571 and being so proactive here!

                    MiroTalkM Offline
                    MiroTalkM Offline
                    MiroTalk
                    wrote last edited by MiroTalk
                    #19

                    @nebulon said in MiroTalk SFU: Recording not possible?:

                    New package is out. Thanks for all the work @mirotalk-57bab571 and being so proactive here!

                    Good! I’m always here to help. Thanks to Cloudron for trusting MiroTalk and supporting us! By the way, I love the new Cloudron UI v.9.0.10, it looks amazing!

                    1 Reply Last reply
                    3
                    • MiroTalkM Offline
                      MiroTalkM Offline
                      MiroTalk
                      wrote last edited by
                      #20

                      PS: Thanks also to @James for his IT support and excellent debugging and suggestions.

                      1 Reply Last reply
                      3
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search