Custom config file

[deizel]

There is a section on the last page of the PuPHPet website about a config-custom.yaml:

You can create a custom config file at puphpet/config-custom.yaml to override anything that you have defined in puphpet/config.yaml. This file is ignored by Git by default. Simply copy the structure from config.yaml and replace the values you want. You can also create completely new keys to define functionality not present in PuPHPet by default!

Though I've used PuPHPet for several months now, this was completely new to me this time around.

You might want to add support for a puphpet-custom.yaml (ignored by VCS) somehow, or add instructions about creating a puphpet/config-custom.yaml (which currently works and is already ignored by VCS).

One specific use case for this would be a single developer overriding the shared folder type (e.g. the repo would set it to 'default', which works on Windows, but the developer might choose 'nfs' which works well on OS X).

Alternatively, there may be other ways to use/abuse this file for the projects needs.

Let me know your thoughts on this and I can look into it.

[beporter]

The config-custom.yaml file being added was a result of a conversation I was actually a part of: puphpet/puphpet#1370 (comment)

Personally, I think the way it was added was lazy and will ultimately cause more problems than it solves. I'm not exactly enthusiastic about supporting it, but it's part of puphpet and I'd like not to make these projects philosophically different from our "parent".

It'd really just be a small addition to PuphpetReleaseInstaller::copyConfigFile() over in the puphpet-release-composer-installer project to look for /puphpet-custom.yaml and copy that too when it's present, so that's probably what we should do.