PHPackages                             su-sws/stanford\_install\_tasks - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. su-sws/stanford\_install\_tasks

AbandonedArchivedDrupal-library[Utility & Helpers](/categories/utility)

su-sws/stanford\_install\_tasks
===============================

A Drupal feature.

7.1.7(6y ago)030GPL-2.0+PHP

Since Jun 28Pushed 6y ago7 watchersCompare

[ Source](https://github.com/SU-SWS/stanford_install_tasks)[ Packagist](https://packagist.org/packages/su-sws/stanford_install_tasks)[ RSS](/packages/su-sws-stanford-install-tasks/feed)WikiDiscussions 7.x-1.x Synced yesterday

READMEChangelog (10)Dependencies (1)Versions (9)Used By (0)

[Stanford Installation Tasks](https://github.com/SU-SWS/stanford_install_tasks)
===============================================================================

[](#stanford-installation-tasks)

##### Version: 7.x-1.8-dev

[](#version-7x-18-dev)

iTasks Installation Tasks
=========================

[](#itasks-installation-tasks)

*A collection of small chunks of code.*

Used in conjunction with the [iTasks installation profile](https://github.com/sherakama/itasks) to provide granular installation tasks.

Theory
------

[](#theory)

Do one thing. And do it well! The concept behind this collection of code is to do one thing per file. This way the amount of change any one thing has is minimal. A smaller footprint will help with encapsulation and decoupling.

This collection of code should be sharable and re-usable. Keeping tasks well named and namespaced will help to reduce duplication of effort and collisions as multiple parties contribute to the shared code bank.

Creating a new namespace
------------------------

[](#creating-a-new-namespace)

When creating a new namespace for your installation profile be unique. An organization name, url, or group might help. For us at Stanford we have many sub groups and created a many level namespace: Eg: Stanford\\WebServices\\Jumpstart\\JumpstartAcademic

This namespace would be for Stanford's Web Services group's Jumpstart Academic distribution from the Jumpstart distribution line.

Please follow PSR-4 naming conventions:

Creating a new install task
---------------------------

[](#creating-a-new-install-task)

Please follow PSR-4 naming conventions:

Install tasks should always be placed in an `Install` folder and then named descriptively. Install task files should always be named the same as the class name. The class should always extend \\ITasks\\AbstractInstallTask. The AbstractInstallTask class is found in the installation profile and not in this repository. Each install task has one required method called `execute`. Please see the boilerplate code below.

```