Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)

Directory Tree

The ideal workflow is to put [Composer] in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central [Composer] install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a [Composer] documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

[…] (link to full page)