Change folder permission about heroku-buildpack-run HOT 4 CLOSED

Hi, yes, the permissions will not be set, because the build is performed in a separate sandboxed build container, and changes you make to the environment of this build container (e.g. environment variables and file permissions) are not propagated to the production containers (dynos), only the raw files of your application are copied to the production dynos.

The solution to your problem is to use a .profile file: create the file .profile in the root directory of your app and put the command chmod -R 777 Storage in it. This file will be sourced at the startup of each production dyno, and your permissions will be set at production time. This is described here.

from heroku-buildpack-run.

Thanks for the help man =)

from heroku-buildpack-run.

Good to know that it worked for you 👍

from heroku-buildpack-run.

@weibeld sir a little help
i got procfile like

web: chmod 777 docker_build.sh && ./docker_build.sh && python main.py --port=$PORT

after deploy run ls -al it still rwx

-rwx------ 1 u59997 dyno 12605504 Apr 13 21:11 ./ksubdomain

when build it is
-rwxrwxrwx 1 root root 12605504 Apr 7 09:56 ./ksubdomain

from heroku-buildpack-run.