How does one handle custom modules in 7.x? about drupal-project

[tobiasbaehr]

You can do it so:
(preserve-paths is for derhasi/composer-preserve-paths)

"installer-paths": {
      "web/": ["type:drupal-core"],
      "web/sites/all/modules/custom/my_custom_module/": ["vendor/my_custom_module"],
      "web/sites/all/themes/custom/my_custom_theme/": ["vendor/my_custom_theme"],
      "web/sites/all/modules/contrib/{$name}/": ["type:drupal-module"],
      "web/sites/all/themes/contrib/{$name}/": ["type:drupal-theme"],
      "web/sites/all/libraries/{$name}/": ["type:drupal-library"],
      "web/sites/all/drush/{$name}/": ["type:drupal-drush"],
      "web/profiles/{$name}/": ["type:drupal-profile"]
},
"preserve-paths": [
      "web/sites/all/modules/contrib",
      "web/sites/all/modules/custom",
      "web/sites/all/themes/contrib",
      "web/sites/all/themes/custom",
      "web/sites/all/libraries",
      "web/sites/all/drush",
      "web/sites/default/settings.php",
      "web/sites/default/files"
]

[dsdeiz]

I guess this approach would be a little bit difficult to manage i.e. you need to provide a composer.json file for your custom modules and you'll need to explicitly list each one of them inside the installer-paths block.

[greg-1-anderson]

Answered accurately; closing.

[hawkeyetwolf]

To make it a little easier, you can put all your custom modules in one repo, same for themes. That way you don't need to have separate repo's and composer.json entries for each individual custom theme/module.