Skip to content

avoid tar extraction failure if wp-content is bind-mounted read-only #281

@drzraf

Description

@drzraf

Bind-mounting the whole wp-content is useful (for plugins, themes, medias, ...), especially if sharing it or testing purpose.
Bind-mounting read-only has its own use (readonly version of the website, development, debugging, ...)

Sadly the current call to tar also extract wp-content/plugins/akismet and wp-content/themes/twenty*which are, AFAICT, the only upstream directories inside wp-content.
These breaks if wp-content is bind-mounted readonly.

Could we think about a way to optionally omit extraction of wp-content? (environment?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    RequestRequest for image modification or feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions