Skip to content
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

Ignore private files. #920

Merged
merged 1 commit into from
Jan 6, 2017
Merged

Conversation

danepowell
Copy link
Contributor

@danepowell danepowell commented Jan 5, 2017

When creating a new project with BLT following these instructions, after the local:setup step I get a /files-private directory in the repo root that should be gitignored.

I'm not quite sure why this directory is created in the repo root instead of in the Drupal docroot. This PR seems like it would put it into the docroot: #322 🤷‍♂️

Regardless, I'm definitely not seeing it at docroot/sites/*/files-private, which is where BLT apparently expects it to be following #732, so I figure we should change to the gitignore to match reality.

@dpagini under what circumstances were you seeing files show up at docroot/sites/*/files-private? I'm guessing it was for an older version of BLT?

@grasmash grasmash added in progress Enhancement A feature or feature request labels Jan 5, 2017
@dpagini
Copy link
Contributor

dpagini commented Jan 6, 2017

I think I was operating off an incorrect assumption, actually. This was because the default.local.settings.php file sets the private directory locally. Since the gitignore already had the entry for docroot/sites/*/private, I was thinking this meant the expected place for local private files was that directory.
This makes more sense to me... but then I just wonder what that entry for docroot/sites/*/private is for at all?

@grasmash grasmash merged commit 8b93b68 into acquia:8.x Jan 6, 2017
@dpagini
Copy link
Contributor

dpagini commented Jan 6, 2017

I see this was already merged... but had an after thought... With this setup, you are likely to have only one private files directory for all sites. I don't think multi-site support is fully fleshed out at this point in time, but should the directory be something more like:

$settings['file_private_path'] = $dir . "/files-private/$site_dir"

This would follow more closely the setup of the config/ directory, I think.

If you guys agree I could post a PR with that or create an issue to discuss further. LMK.

cc: @danepowell @grasmash

@danepowell danepowell deleted the feature/private-files branch December 6, 2017 00:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A feature or feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants