What about forks or customized defaults for Trellis/Bedrock?

[retlehs]

what if you're an agency that maintains your own fork of trellis that already has certain things in place that are used on all of your trellis sites? such as:

• wp-cli packages
• certain users/keys for servers
• vault keys for licenses/services

how could you use this trellis cli to create new trellis projects with all of those defaults?

[retlehs]

(the same goes for bedrock)

[retlehs]

in roots/roots-cli#1 we were going to allow for specifying other remotes

[codepuncher]

In #20 we mention about allowing pluggable subcommands so people can extend with their own setups. Sounds challenging though. How about using a config file like ~/.trellis/config.yml that defines things like remotes?

[swalkinshaw]

Right now the CLI downloads the latest release via GitHub. This wouldn't be too hard to support a customized version such as a Git repo. The complication comes from how the CLI is generating the configs right now since it requires the default configs which exist in Trellis. So if someone supplied a custom fork where wordpress_sites.yml was different enough, it might break things.