drush-patchfile | maintaining patches on a Drupal installation | Content Management System library

by davereid PHP Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | drush-patchfile Summary

drush-patchfile is a PHP library typically used in Web Site, Content Management System, Wordpress, Drupal applications. drush-patchfile has no bugs, it has no vulnerabilities and it has low support. You can download it from GitLab, GitHub.

This is a set of Drush commands to help you manage patches on your local Drupal installation. Most developers (should) know about Drush Make files as a way to store data about a site, installation profile, etc. When using Drush Make files, typically you add information about the patches applied to a project in the following way:. These Drush scripts can read a normal Drush make file just fine, and it will only care about projects which have 'patch' defined. You should make sure that the file referenced contains all the patches you need. If you have more than one Drush make file (and most projects do), you can define a patches.make that "includes" the other files. If you are not using Drush make you can just add one Drush make file just for the purpose of documenting your patches. I typically like to add extra comments to give me even more info about each patch, like the issue to the Drupal.org comment where I found the patch, or if the patch has been committed to the module, and noting that I should remove it when I upgrade.

Support

Quality

Security

License

Reuse

Support

drush-patchfile has a low active ecosystem.

It has 32 star(s) with 10 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

drush-patchfile has no issues reported. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of drush-patchfile is current.

Quality

drush-patchfile has no bugs reported.

Security

drush-patchfile has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

drush-patchfile does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

drush-patchfile releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed drush-patchfile and discovered the below as its top functions. This is intended to give you an instant insight into drush-patchfile implemented functionality, and help decide if they suit your requirements.

Check a patch .
Get a patch .
Applies a patch to a directory .
Download a remote patch .
Execute a command on a directory .

Get all kandi verified functions for this library.

drush-patchfile Key Features

No Key Features are available at this moment for drush-patchfile.

drush-patchfile Examples and Code Snippets

No Code Snippets are available at this moment for drush-patchfile.

Community Discussions

Trending Discussions on drush-patchfile

Use drush-patchfile in DDEV environment

QUESTION

Use drush-patchfile in DDEV environment

Asked 2019-Jan-17 at 14:33

In Drupal 7 I use

drush-patchfile

to automatically implements patches when installing/updating module via drush. But in DDEV I don't know how to extend existing drush with drush-patchfile

As you can see on https://bitbucket.org/davereid/drush-patchfile section Installation, I need to clone the repository into

~/.drush

directory and that will append it to existing drush.

On another project without DDEV, I've already done that with creating new docker image file

...

ANSWER

Answered 2019-Jan-16 at 17:02

You can ddev ssh and then sudo chown -R $(id -u) ~/.drush/ and then do whwatever you want in that directory (~/.drush is /home/.drush).

When you get it going and you want to do it repetitively for every start, you can encode the instructions you need using post-start hooks: https://ddev.readthedocs.io/en/latest/users/extending-commands/

Please follow up with the exact recipe you use, as it may help others. Thanks!

Source https://stackoverflow.com/questions/54221189

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install drush-patchfile

Download or git clone this repository into your ~/.drush directory, or wherever your local Drush commands are stored.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: