Package command

[LukeCarrier]

For ease of deployment, it should be possible to have CM execute the following steps to create a package containing Moodle and the appropriate versions of all components specified in the project file.

The command should look a little like the following:

$ componentmgr package --project-file=~/mysite.json --format=(ZipArchive|WebDeploy) --destination=/some/where.zip

I think we'll achieve this by:

• [ ] Using the Git functionality implemented in #2 to fetch the remote refs and checkout the appropriate ref.
• [ ] Introducing a new "moodle.source" key allowing the user to specify which repository should form the base of their Moodle project. We'll default to the moodle/moodle repository on GitHub.
• [x] Introducing a new "moodle.version" key in the project file which will accept some form of pattern specifying the Moodle series, major version, minor version or release number.
• [x] Performing an install based on the project file. We can amend the existing command to handle the project file being out of tree.
• [x] Packaging the whole caboodle into some kind of archive. Since no standard, cross-platform packaging format exists for full stack web applications, we'll have to build something flexible.
  • [x] Support for Microsoft's Web Deploy format via msdeploy
  • [x] Generic

Rejected requirements:

• [x] Caching a copy of the main Moodle source tree under the user's home directory. This mechanism needs to deal with multiple forks.

[LukeCarrier]

Lots of improvements to this today with the implementation (finally!) of ZipArchive as a package format in 2938ddba8da348830c3bb7d70854bc7a0787cc13.

[LukeCarrier]

Deferring the remaining portions of this to the next release, since the zip-based packaging is enough for Floream's needs.