Lrwxrwxrwx 1 chrooted_user psacln 50 Apr 16 11:24 cache -> //shared/public/app/cacheĭrwxrwxr-x 2 chrooted_user psacln 4096 Apr 16 11:23 languagesĭrwxrwxr-x 2 chrooted_user psacln 4096 Apr 16 11:23 mu-pluginsĭrwxrwxr-x 22 chrooted_user psacln 4096 Apr 16 11:23 pluginsĭrwxrwxr-x 3 chrooted_user psacln 4096 Apr 16 11:23 themes rwxrwxr- 1 chrooted_user psacln 434 Apr 16 11:24 wp-config.php rwxrwxr- 1 chrooted_user psacln 124 Apr 16 11:24 index.phpĭrwxr-xr-x 5 chrooted_user psacln 4096 Apr 16 11:24 wp ĭrwxrwxr-x 6 chrooted_user psacln 4096 Apr 16 11:24 app "symlinkPath": "/var/ĭrwxrwxr-x 6 chrooted_user psacln 4096 Apr 16 11:24. i'm not really good in english, and i try to explain myself as I can, sorry if I confused you. I know theses explanations are not very clear, and i aploogize for that. When connected as a chrooted user, the baseDir to the Symlink is correct and is //current/public/.htaccess, however, his content should be /var/The baseDir is actually correct if i let the option baseDir: "shared". I think that if i add /var/thats why i suggested an option specific to chrooted environments, because if does ONLY affect datas INSIDE symlinks files. "I'm just wondering if an option to skip the creating of the dirs every time is a better option, rather than adding such a specific option as you've suggested." When shipit deploy to /, the corresponding path for apache on my Plesk server is /var/However, symlinks are read by apache. As you can see, i am deploying with shipit, using a chrooted user.
0 Comments
Leave a Reply. |