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
  • 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. Support
  3. less permissive volume sharing

less permissive volume sharing

Scheduled Pinned Locked Moved Solved Support
9 Posts 3 Posters 1.1k Views 3 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.
  • R Offline
    R Offline
    Recliner2042
    wrote on last edited by
    #1

    In the docs, it says to chmod 777 any volume you want shared between various apps.

    Is there an easy way to be more restrictive about this? What if I only want two apps to have access, and don't want every local machine user to?

    1 Reply Last reply
    0
    • R Offline
      R Offline
      Recliner2042
      wrote on last edited by
      #2

      I see at the bottom of the page https://docs.cloudron.io/volumes/#sharing there are instructions to share with all users of the media group. Is the chmod 777 really still necessary when doing that? And if I want to be specific about which apps have access, then do I create a new group, add the run-as users to it, and then follow the same instructions for media but with my new group?

      1 Reply Last reply
      0
      • murgeroM Offline
        murgeroM Offline
        murgero
        App Dev
        wrote on last edited by
        #3

        It uses linux permissions, I'd expect that chown'ing the folder(s) in question to yellowtent would be enough - otherwise there isn't much that can be done via cloudron for the volumes. Restrict the folder to the yellowtent user and group (Cloudron's user) and I think that'll be enough - but it wont restrict per-app.

        --
        https://urgero.org
        ~ Professional Nerd. Freelance Programmer. ~

        R 1 Reply Last reply
        0
        • murgeroM murgero

          It uses linux permissions, I'd expect that chown'ing the folder(s) in question to yellowtent would be enough - otherwise there isn't much that can be done via cloudron for the volumes. Restrict the folder to the yellowtent user and group (Cloudron's user) and I think that'll be enough - but it wont restrict per-app.

          R Offline
          R Offline
          Recliner2042
          wrote on last edited by
          #4

          @murgero Thank you. That's what I was thinking. But it wasn't the case. Apps can't write to a directory owned by yellowtent.

          murgeroM 1 Reply Last reply
          0
          • R Recliner2042

            @murgero Thank you. That's what I was thinking. But it wasn't the case. Apps can't write to a directory owned by yellowtent.

            murgeroM Offline
            murgeroM Offline
            murgero
            App Dev
            wrote on last edited by
            #5

            @Recliner2042 oh, does it have to be root? I don't use the shared volumes currently so I wasn't 100% sure, just working of basic Linux Knowledge

            --
            https://urgero.org
            ~ Professional Nerd. Freelance Programmer. ~

            R 1 Reply Last reply
            0
            • murgeroM murgero

              @Recliner2042 oh, does it have to be root? I don't use the shared volumes currently so I wasn't 100% sure, just working of basic Linux Knowledge

              R Offline
              R Offline
              Recliner2042
              wrote on last edited by Recliner2042
              #6

              @murgero I'm pretty sure you have to create a group, place each run-as app-user into that group, and then make the group own the directory. But I'm not an expert at this stuff.

              1 Reply Last reply
              0
              • girishG girish has marked this topic as solved on
              • R Offline
                R Offline
                Recliner2042
                wrote on last edited by
                #7

                @girish did you mark this solved because I got it right in my last post?

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #8

                  @Recliner2042 yes, sorry, I thought the problem was solved. Is that not the case?

                  R 1 Reply Last reply
                  0
                  • girishG girish

                    @Recliner2042 yes, sorry, I thought the problem was solved. Is that not the case?

                    R Offline
                    R Offline
                    Recliner2042
                    wrote on last edited by
                    #9

                    @girish Well, it wasn't exactly a problem. I was just asking an important question, and wanted a confirmation that I guessed the right answer.

                    1 Reply Last reply
                    1
                    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