NGinX by default doesn't have permissions to serve content

[VanDavv]

Due to the current limitations, NGinX won't have access to the filesystem to serve the files correctly and will return 404 when accessing correct path.

Working workaround for this situation is to run /bin/chmod a+x / before the nginx starts but we are in need of more elegant solution as it will be hard for users to guess how to handle that issue.

[mateuszsrebrny]

(Core) (meta for the future, no quick workaround)

[lucekdudek]

@VanDavv do we have any update on this from Core?

[shadeofblue]

to be analyzed within: https://github.com/golemfactory/yagna-sdk-team/issues/205

[shadeofblue]

closing as a duplicate of: https://github.com/golemfactory/yagna-sdk-team/issues/205