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. EspoCRM
  3. make `public` folder writable

make `public` folder writable

Scheduled Pinned Locked Moved Unsolved EspoCRM
6 Posts 3 Posters 1.2k 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.
    • vladimir.dV Offline
      vladimir.dV Offline
      vladimir.d
      wrote on last edited by
      #1

      There are some EspoCRM extensions require a public content being uploaded to /app/code/7.0.8/public folder, which is on read-only filesystem in the cloudron app now.

      Could you amend the app so the public folder was linked to /app/data/public?

      nebulonN 1 Reply Last reply
      0
      • vladimir.dV vladimir.d

        There are some EspoCRM extensions require a public content being uploaded to /app/code/7.0.8/public folder, which is on read-only filesystem in the cloudron app now.

        Could you amend the app so the public folder was linked to /app/data/public?

        nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        @vladimir-d linking the issue in gitlab for reference https://git.cloudron.io/cloudron/espocrm-app/-/issues/1

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

          @vladimir-d actually that folder contains release files and the actual app code, so we can't just link that folder into /app/data as it would be very hard to ensure tested and reliable updates then with new releases. If EspoCRM extensions require to place and patch release files, then I think we can't support those easily without risking to break the app on every update.

          Do you have more information on how the upstream app handles such cases with their extensions?

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

            In the past, we have made change for specific extensions like the VOIP integration - https://git.cloudron.io/cloudron/espocrm-app/-/commit/575567fc72457be3d76d8932e7620b1c849fdd8e

            1 Reply Last reply
            0
            • vladimir.dV Offline
              vladimir.dV Offline
              vladimir.d
              wrote on last edited by
              #5

              I think I was unclear about what folder being made writable, sorry.

              What we need is to deploy some files and directories in /app/code/current/public folder which is readonly now. This /app/code/current/public folder contains just directories/files available for public visitors. We don't need to update or patch release files.

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

                I checked this again, but it seems that the public directory has a bunch of code.

                root@d66257ab-b6ad-4648-acf5-f1dbc2281a80:/app/code/7.2.7/public# find .
                .
                ./oauth-callback.php
                ./robots.txt
                ./index.php
                ./web.config
                ./api
                ./api/v1
                ./api/v1/.htaccess
                ./api/v1/portal-access
                ./api/v1/portal-access/.htaccess
                ./api/v1/portal-access/index.php
                ./api/v1/index.php
                ./portal
                ./portal/.htaccess
                ./portal/index.php
                ./install
                ./install/img
                ./install/img/devices.png
                ./install/js
                ./install/js/install.js
                ./install/css
                ./install/css/install.css
                ./install/index.php
                

                Do you remember what extension writes where? Is it in a subdirectory under public or does it write straight under public itself?

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