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

`lando pull` set files directories with the wrong permissions #1325

Closed
shaal opened this Issue Dec 6, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@shaal
Copy link
Contributor

shaal commented Dec 6, 2018

Bug Report

Tell us about your setup
v3.0.0-rc.1 on Ubuntu 18.10

Tell us about your .lando.yml

name: [...]
recipe: pantheon
config:
  framework: drupal8
  xdebug: true
  env: dev
  site: [...]
  id: [...]
tooling:
  drush:
    cmd:
      - /app/vendor/bin/drush

After running lando pull and choose only files from dev.

Any image from sites/default/files cannot be opened
(The requested URL "[...]/sites/default/files/2018-05/S2912_0.jpg" was not found on this server.)
Unless it's an image that using image_style, and then it opens correctly.

This is what fixed it (need to be done for each directory under /sites/default/files)

  • lando ssh
  • cd /app/web/sites/default/files/2018-05
  • ls -lat and I see that 2018-05 directory is set to 750 (drwxr-x---)
  • chmod 755 . fixes the issue (drwxr-xr-x)

This issue does not happen when I manually download the files from pantheon's backup, and open it with tar xzvf, in that case all permissions are set correctly.

@shaal

This comment has been minimized.

Copy link
Contributor Author

shaal commented Dec 13, 2018

If you already downloaded public files through lando pull,
a quick&dirty solution would be

cd sites/default/files
chmod -R 755 *

@pirog pirog added this to the 3.0.0-rc.3 milestone Feb 1, 2019

@pirog pirog self-assigned this Feb 3, 2019

pirog added a commit that referenced this issue Feb 4, 2019

@pirog

This comment has been minimized.

Copy link
Member

pirog commented Feb 4, 2019

@shaal was finally able to get to this. Can replicate and confirm. Fix will be in next release!

@pirog pirog closed this Feb 4, 2019

pirog added a commit that referenced this issue Feb 5, 2019

pirog added a commit that referenced this issue Feb 5, 2019

pirog added a commit that referenced this issue Feb 7, 2019

pirog added a commit that referenced this issue Feb 7, 2019

Merge pull request #1428 from lando/pirog5007-hyperion
#1325: Added support to run on non port 80 things to dotnet

pirog added a commit that referenced this issue Feb 8, 2019

pirog added a commit that referenced this issue Feb 8, 2019

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