This is an alternative (or auxiliary) issue to #335, I want to use some of the scripts provided by the scaffold tooling repo (e.g drush, backup, sync backups, etc) without being locked into version constraints or additional modules that I don't want on my PaaS project.
This could also include the settings files, but scripts is the highest priority IMO.
Instead of bundling scripts with module requirements, you could have a separate govcms/scaffold-scripts (or whatever) to make this easier to manage on PaaS
This is an alternative (or auxiliary) issue to #335, I want to use some of the scripts provided by the scaffold tooling repo (e.g drush, backup, sync backups, etc) without being locked into version constraints or additional modules that I don't want on my PaaS project.
This could also include the settings files, but scripts is the highest priority IMO.
Instead of bundling scripts with module requirements, you could have a separate govcms/scaffold-scripts (or whatever) to make this easier to manage on PaaS