All paths in configs must be expanded
Closed
All paths in configs must be expanded
Created by: qfox
If I pass symlinked path to configs my hooks doesn't work properly. Really discouraged bug. Probably it could be easily fixed on the config/initializers layer.
Created by: qfox
Use case: If you put git home directory to another device and symlink that to /home/git it will skip all push events because post_receive will send real path to repo. And PostReceive::perform will not work. I see it in logs.
By Administrator on 2013-02-08T01:31:15 (imported from GitLab project)
Created by: zzet
@zxqfox Can you get more information?
We put git homedir into var:
/var/git
All repositories are placed into/var/git/repositories
App placed in/some_dir/gitlab/releases/release_num/
As you see, we not use default configs, but all is good.
By Administrator on 2013-02-26T10:52:31 (imported from GitLab project)
Created by: qfox
@zzet I'm sure you will catch that bug when you move /var/git to /other/var/git, and then make a symlink from original to other path.
mv /var/git /other/var/git && ln -s /other/var/git /var/git
. I think the real trouble with symlinks because name of repo calculates from paths.By Administrator on 2013-02-26T12:52:05 (imported from GitLab project)
Created by: zzet
No. At first time we placed
git
user homedir on/home/git
and created symlink to repositories:ln -s /var/git/repositories /home/git/repositories
. No problems founded.@zxqfox why you create symlink? mb better to edit
/etc/passwd
with newhomedir
path?By Administrator on 2013-02-26T12:57:55 (imported from GitLab project)
Created by: dosire
Moved to http://feedback.gitlab.com/forums/176466-general/suggestions/3788046-support-symlinked-paths
By Administrator on 2013-03-27T08:56:47 (imported from GitLab project)