Difference between revisions of "Profiles"
Jump to navigation
Jump to search
(→Basics) |
|||
| Line 10: | Line 10: | ||
* [https://drupal.org/node/1356276 Make install profiles inheritable] | * [https://drupal.org/node/1356276 Make install profiles inheritable] | ||
* [http://www.phase2technology.com/blog/inheriting-your-drupal-profile-from-an-existing-distribution/ Inheriting your Drupal profile from an existing distribution] | * [http://www.phase2technology.com/blog/inheriting-your-drupal-profile-from-an-existing-distribution/ Inheriting your Drupal profile from an existing distribution] | ||
| + | |||
| + | * [[Builds]] | ||
== Profiler == | == Profiler == | ||
Revision as of 14:50, 24 November 2013
Basics
See also Drush#Make
- Developing installation profiles
- Install Profile Packaging
- Packaging a profile on drupal.org (make file -> install profile)
Profiler
Enables the use of .info like syntax for profiles.
Aegir workflow
It's not best practice to try and store build .make and .profile/.info in the same repo. This would require one to set the profile download in the make file the be the same repo, thus causing Drush to download all .make projects twice.
Instead, a stub build .make file that points to said repo will download all properly. technique copied from mig5.
My profiles
See my Github
- Base dev - old
to check;