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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Moodle
  3. Moodle 5.1.1 App – Missing vendor/ Folder (?)

Moodle 5.1.1 App – Missing vendor/ Folder (?)

Scheduled Pinned Locked Moved Moodle
2 Posts 2 Posters 34 Views 2 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.
  • osoboO Offline
    osoboO Offline
    osobo
    wrote last edited by
    #1

    Dear Cloudron team,

    I’ve noticed that in the current Moodle 5.1.1 package on Cloudron, the vendor/ directory is missing under /app/code. This triggers the following error when updating some plugins:

    Composer dependencies were not found. Make sure the "composer install --no-dev --classmap-authoritative" command has been run in the Moodle root directory. If you are not using Composer, make sure the vendor directory exists and contains the necessary files.

    Moodle still runs fine, but it looks like the Composer dependencies may not be bundled correctly in the app image.

    Could you please check if the Moodle package should include the vendor/ folder, or adjust the next build process so Composer dependencies are installed during packaging?

    Thanks for your support!

    1 Reply Last reply
    0
    • J Online
      J Online
      joseph
      Staff
      wrote last edited by
      #2

      @osobo Moodle package has quite a complicated setup. The app has over 25 (!) plugin types and each plugin writing all over the source code. For this reason, source code is treated as data.

      /app/code is just the released tarball.

      The app runs off /app/data/moodle .

      The package seems to make some best effort update by copying latest /app/code into /app/data/moodle .

      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