-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move scripts into a separate package #341
Comments
Nice one @acbramley, I believe @steveworley also advocated for a similar approach. We'll raise and see if we can get some approvals to press forward with this. |
Hey @acbramley — thanks for the suggestion, after the last release I was considering the same. I've got an internal ticket to track this. I'm hoping that we can get this started soon. |
@steveworley Awesome! In case this helps anyone else, in the mean time I'm doing this in my CLI dockerfile:
|
Dockerfile ninja points for copying the scripts into a folder in your image and link/run from there
|
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
The text was updated successfully, but these errors were encountered: