Skip to content
This repository was archived by the owner on Aug 20, 2019. It is now read-only.
This repository was archived by the owner on Aug 20, 2019. It is now read-only.

Config option to allow the vagrant user to write to additional directories #479

Description

@klonos

Problem/Motivation

Backdrop CMS has its directories for contrib/custom modules and themes directly under the docroot (as opposed to Drupal 7, which is under /sites/[whatever]/files).

Steps to reproduce

Use the Project Browser that's available in core Backdrop CMS to install any contrib module/theme.

Expected behaviour

I would expect that it would be possible to install modules/themes via the UI.

Actual behaviour

When trying to install modules/themes via the UI, you get a "Permissions are not set up properly." error.

Proposed changes

Ideally: detect that this is a Backdrop installation and automatically configure permissions for the /modules, /themes and layouts directories.

Alternatively: provide a config option to specify additional directories within the docroot, where the vagrant user has write permissions

Activity

  1. klonos commented on Oct 16, 2018

    @klonos
    Author

    @thom8 in #442 (comment) you mentioned this:

    ... you could create a pre provisioning task which allows access to other directories...

    How does one go about doing that?

  2. thom8 commented on Nov 3, 2018

    @thom8
    Member

    @klonos you can create pre & post provisioning tasks with ansible -- https://beetbox.readthedocs.io/en/latest/configuration/ansible/custom-tasks/

    You can see some example in this project for setting folder permissions eg. https://github.com/beetboxvm/beetbox/blob/master/provisioning/ansible/playbook-config.yml#L67-L74

    and further info in the ansible file module --https://docs.ansible.com/ansible/latest/modules/file_module.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions