Skip to content

Move scripts into a separate package #341

@acbramley

Description

@acbramley

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    CAB pendingAppending decision from the GovCMS CAB

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions