ContentServer

Differences between revisions 5 and 8 (spanning 3 versions)
Revision 5 as of 2007-11-02 20:16:20
Size: 3912
Editor: 12
Comment:
Revision 8 as of 2009-03-04 17:38:47
Size: 4547
Editor: chance
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''Packages affected''': moodle  * '''Packages affected''': moodle, moodle-server-standalone, edubuntu-content-server
Line 10: Line 10:
We will make it easier to install Moodle in Edubuntu as part of a content server solution for educators. We will reduce the number of installation questions via preseeding; if Recommends: are still not supported for hardy we will create a moodle-standalone metapackage to provide a single package install that results in a working Moodle. We will make it easier to install Moodle in Edubuntu as part of a content server solution for educators. We will reduce the number of installation questions via preseeding; if Recommends are still not supported for hardy we will create a moodle-standalone metapackage to provide a single package install that results in a working Moodle with configured database.
Line 16: Line 16:
The existing moodle package still has some rough edges, and there must be a straightforward way to install Moodle and the choice offerings in other content server areas on an Edubuntu system. The existing moodle package still has some rough edges, and there must be a straightforward way to install Moodle with its and the choice offerings in other content server areas on an Edubuntu system.
Line 19: Line 19:
 * Marjorie downloads the Ubuntu Education CD to transform her Ubuntu server into an education content server. Marjorie will be instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no debconf questions will be asked.  * Marjorie downloads the Ubuntu Education CD to transform her Ubuntu server into an education content server. Marjorie will install the edubuntu-content-server package from the edubuntu CD and is instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no debconf questions will be asked.
Line 22: Line 22:
== Assumptions == == Design ==
Line 24: Line 24:
== Design ==
 * the edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle, wiki, gobby, etc.)
 * The edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle-server-standalone, wiki, obby, etc.).
 * The moodle-server-standalone metapackage will use proper preseeding values to install a database, webserver and moodle with the least set of needed debconf questions.
Line 28: Line 28:
 * Recommends: will be honored in the near future, so the existing package will begin installing the database server correctly.
 * The existing Moodle has quite a number of other projects' sources included in the upstream source; these should be broken out and packaged separately, and the moodle package should add these as dependencies. It would be nice to complete this process, and we will get as close as we can by hardy's release. (See BoF agenda & discussion below.)

* Recommends will be honored in the near future, so the existing package will begin installing the database server through that.
 * The existing Moodle has quite a number of other projects' sources included in the upstream source; these should be broken out and packaged separately, and the moodle package should add these as dependencies so security updates get easier. It would be nice to complete this process, and we will get as close as we can by hardy's release. (See BoF agenda & discussion below.)
Line 32: Line 33:
 * We will modify the set of debconf questions to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.
* We will modify the set of debconf questions and add properly preseeded values where necessary to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.
Line 36: Line 38:
== Outstanding Issues == Install an ubuntu LAMP server.
Install the edubuntu-content-server package on top.
Browse to http://localhost/moodle/ and run the php configuration part to finish the installation.
Check moodle runs correctly after this procedure.
Line 57: Line 62:
Line 60: Line 64:
CategoryEdubuntu

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad Entry: edubuntu-content-server

  • Packages affected: moodle, moodle-server-standalone, edubuntu-content-server

Summary

We will make it easier to install Moodle in Edubuntu as part of a content server solution for educators. We will reduce the number of installation questions via preseeding; if Recommends are still not supported for hardy we will create a moodle-standalone metapackage to provide a single package install that results in a working Moodle with configured database.

Release Note

The edubuntu-content-server package handles all the heavy lifting to create a server for many kinds of educational content; e.g., interactive course materials and assignments, collaborative documents, and locally cached wikipedia articles can live right here on your very own server.

Rationale

The existing moodle package still has some rough edges, and there must be a straightforward way to install Moodle with its and the choice offerings in other content server areas on an Edubuntu system.

Use Cases

  • Marjorie downloads the Ubuntu Education CD to transform her Ubuntu server into an education content server. Marjorie will install the edubuntu-content-server package from the edubuntu CD and is instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no debconf questions will be asked.

  • Shamu starts Synaptic and selects the 'moodle' package for installation. She is asked a minimum of debconf questions and a working Moodle is the result.

Design

  • The edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle-server-standalone, wiki, obby, etc.).
  • The moodle-server-standalone metapackage will use proper preseeding values to install a database, webserver and moodle with the least set of needed debconf questions.

Implementation

  • Recommends will be honored in the near future, so the existing package will begin installing the database server through that.
  • The existing Moodle has quite a number of other projects' sources included in the upstream source; these should be broken out and packaged separately, and the moodle package should add these as dependencies so security updates get easier. It would be nice to complete this process, and we will get as close as we can by hardy's release. (See BoF agenda & discussion below.)

Code Changes

  • We will modify the set of debconf questions and add properly preseeded values where necessary to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.

Test/Demo Plan

Install an ubuntu LAMP server. Install the edubuntu-content-server package on top. Browse to http://localhost/moodle/ and run the php configuration part to finish the installation. Check moodle runs correctly after this procedure.

BoF agenda and discussion


CategorySpec CategoryEdubuntu

Edubuntu/Specifications/ContentServer (last edited 2010-01-21 15:26:43 by 196-210-177-89-wblv-esr-3)