Distributions

Training is a Drupal distribution for building Drupal based training websites / portal which brings together information about diverse courses (Drupal, PHP, Soft Skills, Personality Development etc.) in a unified way.

Training distribution contains most of the modules and basic configuration (content-types, views, features) you would need to create a training portal.

The core features of Training include :

• Inbuilt Roles - Trainer, Trainee.
• Inbuilt Vocabulary – Courses.
• Inbuilt Content Types - Course Topic, Course SubTopic, Course Assignments, Training, Training-Calender.
• Inbuilt Block – Courses taxonomy-view.
• Inbuilt Views - Calendar, Courses Listing, Topic-SubTopic Listing.
• Each course has a dedicated page, listing topic - sub topics with links having detailed description.
• The most interesting feature of this distribution is that Trainer can upload multiple videos, pdfs, documents under Course Topic and Course Sub-topic which Trainees can watch / read whenever they want.
• Trainers can schedule the trainings on various courses / topics / sub-topics with the help of Training-Calender content-type.
• Customizable home page with calendar view displaying all the scheduled trainings.

A list of Drupal distributions for education

• ELMS
• Julio
• Open Academy
• Open Scholar

See also EduERP on Drupal Groups.

Instructions for installing distributions / installation profiles on your Quickstart machine.

Using Commerce Kickstart as an example

1. cd /home/quickstart
2. wget http://ftp.drupal.org/files/projects/commerce_kickstart-7.x-1.4-no-core.tar.gz
3. tar -zxvf commerce_kickstart-7.x-1.4-no-core.tar.gz
4. drush qc --domain=dcqs.dev --profile=commerce_kickstart --makefile=~/commerce_kickstart/distro.make

extra info:

• use the no-core files
• urls of latest releases can be found under the 'View all releases' link at the bottom of every distributions project page.

Based on this article.

Installation profiles are like modules

All installation profiles must have profilename.info and profilename.profile files, and they can also have a profilename.install file. The profilename.profile file has access to almost everything a normal Drupal modulename.module file does because Drupal is fully bootstrapped before almost anything in the profile runs. The main exception is that st() should generally be used to translate strings instead of the usual t() because the localization hasn't been set up until the installation process completes.

.info file

The profilename.info file should look similar to this:

So you want to provide a Distribution on Drupal.org? Great! The Drupal.org packaging system will take the code for a project, assemble it into an easily downloadable format, and post it to the project's pages on Drupal.org.

Here are the steps:

1. Assemble the pre-requisites
2. Create a Drush Make file
3. Convert to a Drupal.org-specific Drush Make file
4. Build and verify it works
5. Commit your code to Git
6. Release your code on Drupal.org
7. Maintain your distribution

Step 1: Pre-requisites

• Drush 5.x+.
• Drupal.org Drush, a Drush extension which is required for running tests on makefiles. See this post for installation instructions.
• A full project node on Drupal.org, of project type "Distribution".

Step 2: Drush Make file

There are several Drupal projects that can be used to help you create an installation profile.

Drush make

Drush make (included as part of the drush project since Drush 5) is a command-line packaging tool specifically designed for Drupal. It natively supports downloading, unpacking, and installing Drupal modules and themes via a simple configuration file (the 'make' file), and a single command. Drush make is the tool used by the Drupal.org packaging system to create packaged distributions, and is a very useful tool to have in your local development environment for generating, formatting, and verifying .make files you'll eventually commit to your profile.

For more information about using drush make see Packaging a distribution on Drupal.org.

Features

The Features module is increasingly the core of install profiles, providing tools for creating diverse types of configuration, from content types and fields to views and user permissions.

Apps