It would be nice if the prefix of user repositories would be customizable. Right now
user repositories are created under ~username/.
I am trying this together with other web tools and most stumble over repository directories
with the tilde. It would be good if the prefix of the username could be changed. It
might even be a directory.
Reported by f.zschocke on 2013-07-03 18:51:22
The text was updated successfully, but these errors were encountered:
I am in the process of setting up Git servers and am running mutliple tools on the same
repository space, i.e. directory. For one, in order to evaluate them against each other
and also to fulfill different tasks, like repository management and code review.
While some tools like cGit have no problems with directories with a tilde, pother like
GitLab have a problem importing repositories from directories with it. So in order
to get different tools to get along with each other, it would be beneficial if such
things as the namespace for user repositories could be configured by a setting.
Checking the code, it looks to me that it would only involve a change in UserModel,
altering getPersonalPath() and making sure this method is used as the only means to
get the personal path. When you say that is actually an involved change, what am I
I was going to try and change that but wanted to check what trouble I'm in for beforehand.
Okay, answering this myself, there are actually quite a few places where the "~" is
hard coded. Changing my question:
Is this only hard coded in Java sources or also in .js or .html files? (I know nothing
about web development so please excuse me if this is a stupid question.)
Branching off of v1.2.1 I have now started to implement this. I have refactored the
code to gather all logic concerning the path of a user personal repository into one
Let me know if you are at all interested in this. If so, I would rebase this onto master
and send you a pull request for review. At least the refactoring part could be interesting.
Making it a setting is a bit more involved as I would have to cover cases like an empty
prefix or a directory prefix and test that.
I'll give this some thought. I may be open to making it configurable - it will depend
on how cleanly (i.e. reasonable class dependencies) it can be done. I'm not sure about
supporting the blank prefix. Perhaps.
This week, however, I am not thinking about new features; just trying to get 1.3.0
I have pushed some changes to GitHub concerning this issue. I would like your opinion
on this, to see if this is anything that you would be willing to go forward with and
that is worth developing into a pull request.