| Configuring a project | User guide | Installing a project |
|---|
There are three different types of codebases you can build.
Functional codebase: Build codebase by download of a release package.
Developer codebase: Build codebase by symlinking to the lib/ folder.
Distribution codebase: Build codebase intended to be packaged for release.
execute ./toolkit/phing build-platform
This build downloads the latest released platform deploy package depending on what version you specified as the platform.package.version property. After download it is unpacked to the build folder. This build is mainly used by subsites that need to test their code on a specific platform version.
execute ./toolkit/phing build-platform-dev
Build the actual codebase, this will transform your lib/ and
resources/ folder into a Drupal codebase which you can installed. This action by
default will start by backing up any site specific files if there were any
present.
Currently platform-dev has not migrated to the toolkit yet for building their codebase. This is a work in progress. If you are developing for a subsite this part of the documentation does not apply to your codebase.
execute ./toolkit/phing build-platform-dist
Build the distribution files for a single profile. You can change the profile
either through changing the property in your build properties file or through
defining it in the command itself with the -D 'profile'= option.
This build will only build the files necessary for deployment and the result
will be compressed and uploaded to github when your project gets tagged
for release. After the release this package will be available for download by
the ./toolkit/phing build-platform command.
execute ./toolkit/phing build-subsite
This build downloads and unpacks the latest released subsite deploy package and
unpacks it to the build/sites/default folder. This build will be mainly used
by platform who need to test subsite configurations on their codebase.
This build will download the latest release package of the version you define in your build properties file. Currently subsites are not yet using the release assets for deployment so the command will not give you any code.
execute ./toolkit/phing build-subsite-dev
Builds all resources and symlinks the individual modules, themes and libraries
to their location in the lib/ folder. The build/sites/default folder effectively becomes a
mirror of lib/.
execute ./toolkit/phing build-subsite-dist
Build the distribution files for a single subsite, you can change the subsite
either through changing the property in your build properties file or through
defining it in the command itself with the -D 'subsite'= option.
This build will only build the files necessary for deployment. The result of the
build will be compressed and uploaded to github when your project gets tagged
for release. After the release this package will be available for download by
the ./toolkit/phing build-subsite command.