I attempted the manual installation by following the outlined steps here. However, there is no mentioning of what files or folders need to be writable. So whenever I want to conclude the installation all I receive is an empty response.
Only difference was that I downloaded release 2.8.1 here from Github.
Could you give some pointers, as it's normally considered bad practice to make just everything writable.
Hi,
first of all thanks for providing Piwigo!
I attempted the manual installation by following the outlined steps [here](http://piwigo.org/basics/installation_manual). However, there is no mentioning of what files or folders need to be writable. So whenever I want to conclude the installation all I receive is an _empty_ response.
Only difference was that I downloaded release 2.8.1 here from Github.
Could you give some pointers, as it's normally considered bad practice to make just everything writable.
<!-- github-sync-id:158904349 -->
Hello
Thank you
for such remark/debate/help, don't hesitate to use our forum instead of a github bug report : you can found threads such as http://piwigo.org/forum/viewtopic.php?id=25375 which will answer to your concerns, and if you still want to debate open a new thread there.
Hello
Thank you
for such remark/debate/help, don't hesitate to use our forum instead of a github bug report : you can found threads such as http://piwigo.org/forum/viewtopic.php?id=25375 which will answer to your concerns, and if you still want to debate open a new thread there.
<!-- github-comment-id:224261739 -->
Actually I think this issue is relevant on Github, because it is directly related to Github downloadable version of Piwigo. If @assarbad had downloaded Piwigo from Piwigo.org, he won't have encountered the same problem: during release build, the permissions are modified, see https://github.com/Piwigo/Piwigo/blob/master/tools/pwg_rel_create.sh#L112
In the repository README we should add a section "install from Github"
Actually I think this issue is relevant on Github, because it is directly related to Github downloadable version of Piwigo. If @assarbad had downloaded Piwigo from Piwigo.org, he won't have encountered the same problem: during release build, the permissions are modified, see https://github.com/Piwigo/Piwigo/blob/master/tools/pwg_rel_create.sh#L112
In the repository README we should add a section "install from Github"
<!-- github-comment-id:224264762 -->
@plegall: a link to that script inside the README might help as well. Thanks for the pointer, that helps me a lot!
@plegall: a link to that script inside the README might help as well. Thanks for the pointer, that helps me a lot!
<!-- github-comment-id:225454317 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi,
first of all thanks for providing Piwigo!
I attempted the manual installation by following the outlined steps here. However, there is no mentioning of what files or folders need to be writable. So whenever I want to conclude the installation all I receive is an empty response.
Only difference was that I downloaded release 2.8.1 here from Github.
Could you give some pointers, as it's normally considered bad practice to make just everything writable.
Hello
Thank you
for such remark/debate/help, don't hesitate to use our forum instead of a github bug report : you can found threads such as http://piwigo.org/forum/viewtopic.php?id=25375 which will answer to your concerns, and if you still want to debate open a new thread there.
Actually I think this issue is relevant on Github, because it is directly related to Github downloadable version of Piwigo. If @assarbad had downloaded Piwigo from Piwigo.org, he won't have encountered the same problem: during release build, the permissions are modified, see https://github.com/Piwigo/Piwigo/blob/master/tools/pwg_rel_create.sh#L112
In the repository README we should add a section "install from Github"
Indeed from Github that's different, at least for Linux users
@plegall: a link to that script inside the README might help as well. Thanks for the pointer, that helps me a lot!