#WORK
#WORK

_library/index-include.md.cms

_library/sitemap-include.md.cms

2023-01-01 :: Page #9 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #9 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #8 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #8 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #7 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #7 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #6 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #6 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #5 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #5 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #4 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #4 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #3 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #3 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #2 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #2 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #1 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #1 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

2023-01-01 :: Page #0 in 2023 – Gary B. Genett; Author 1; Author 2; Author 3

Lorem Ipsum #0 in 2023

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

[…] (link to full page)

  • ITEM 1
  • ITEM 2
  • ITEM 3

RIGHT BOX

RIGHT TEXT