Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Directory permissions for releases post 4.0 release

See original GitHub issue

Using version ^4 my release directory looks like this drwx------ 8 deploy deploy 4096 Apr 15 17:39 20180415052742/

Using version ^1 my release directory looks like this. drwxrwxr-x 8 deploy deploy 4096 Apr 15 17:57 20180415054603/

This breaks things for me where I have a www-data user reading from releases, post version 4 it can’t get to my release directories at all. Is there a workaround for this ?

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:10 (6 by maintainers)

Top GitHub Comments

2reactions

silentworkscommented, May 14, 2018

Yeah I am experiencing this same issue, I just create an extra task to change the permission based on the published event being fired.

shipit.on('published', async () => {
  shipit.log(chalk.green('Changing directory permissions.'))
  await shipit.remote(`chmod +x ${shipit.releasePath};`);
  shipit.log(chalk.green('Permissions changed'))
})

1reaction

gregbergecommented, Apr 16, 2018

OK, I don’t know what could be the problem, could you try to investigate?