Repository list page is empty

[GoogleCodeExporter]

After upgrading to 1.6.0, the page "Repositories" <http://xxx/repositories/> 
shows no repository at all (see screenshot attached).

There are 3 repositories in the system.  They were created with 1.3.2.  I then 
upgraded to 1.5.1, then to 1.6.0.  The server output says (when loading that 
page):

2014-06-18 07:51:53 [INFO ] 3 repository models loaded for fgeorges in 4 msecs

I am not sure how to get more info.  I tried to change 
[data]/temp/webapp/log4j.properties, but it gets overridden after a restart, 
and I can't find the files logs/gitblit.log and logs/gitblit.html.

Original issue reported on code.google.com by fgeorges on 18 Jun 2014 at 6:02

Attachments:

• [Screen Shot 2014-06-17 at 18.54.10.png](https://storage.googleapis.com/google-code-attachments/gitblit/issue-448/comment-0/Screen Shot 2014-06-17 at 18.54.10.png)

[GoogleCodeExporter]

It sounds like these repositories might be user repositories (under 
~username/repo.git). 1.6.0 includes a new option that hides user repositories 
from the main list by default. If you click on your user icon and select "My 
profile" you should seem them listed.

If you wish to change this there is a new preference you will need add manually.

    # Setting to include personal repositories in the main repositories list.
    #
    # SINCE 1.6.0
    web.includePersonalRepositories = false

This change was in response to issue 419.

Original comment by gib...@gmail.com on 20 Jun 2014 at 7:47

[GoogleCodeExporter]

Thank you, the repositories were indeed user repositories.  Changing the option 
made them visible again.

I might need to read the documentation again, as if I remember correctly, 
Gitblit rejected any other name than "~myself/something" for a new repository, 
with 1.3.1, even though I would have preferred "project/repo-name" instead.

Thanks for your help!

Original comment by fgeorges on 22 Jun 2014 at 6:04

[GoogleCodeExporter]

Currently, non-admin users are only permitted to create repositories in their 
personal namespace (~username).  I'm working on more flexible permissions for 
administering repos & projects (ticket-75).

Original comment by James.Mo...@gmail.com on 24 Jun 2014 at 4:24

• Changed state: Done

[GoogleCodeExporter]

Thank you!

So if I am right, the admin is supposed to create non-personal repositories, 
and then assign people to them (instead of having a regular user creating a 
repo, choosing whether it is personal or not...)

Is there any way to "move" a personal repo to another "location", say from 
"~jdoe/abc-xyz-component" to "abc-project/xyz-component" ?

Original comment by fgeorges on 24 Jun 2014 at 5:06

[GoogleCodeExporter]

Yes... but only an admin can move repos in <= 1.6.0.

1.6.0 has laid some of the groundwork required to improve project management 
(e.g. the project selector during new/edit repo) and 1.7.0 will carry that to 
it's logical conclusion.

https://dev.gitblit.com/tickets/gitblit.git/75

Original comment by James.Mo...@gmail.com on 24 Jun 2014 at 5:42

[GoogleCodeExporter]

Excellent, thank you James!

Will look at it in 1.7.0.  By the way, I just realised that in 1.6.0, the name 
of the repo (e.g. in "bew repo" or in the repo properties screen) is not a 
free-text field anymore, but has a "project" dropdown list (which by the way 
makes the ```use '/' to group repositories. e.g. libraries/mycoollib.git``` 
rather useless, doesn't it?)  In my instance it is provisioned with the current 
logged user (e.g. `~admin/`).

Is there any way to create a project, without being a user?

PS: Sorry for the delay in responding, I did not see any notification from 
Google Code...

Original comment by fgeorges on 5 Jul 2014 at 3:33

[GoogleCodeExporter]

> which by the way makes the ```use '/' ...``` rather useless, doesn't it?

Nope.  It actually works just about the same.  If you wanted to nest into 
/nested/dir/ you would enter that into the text field: nested/dir/myrepo.git.  
That would create the project "nested" (and remaining dir structure), if it 
didn't exist.

In 1.6.0 it still works the same way.  Except now if you want to create a new 
repo (or move a repo) in "nested", you can select it - if it already exists.  
Otherwise pick '/' and enter it like before: nested/dir/myrepo.git.

The project selector is part of the ground work for project management.

As before, you can only create a non-personal repo if you are an administrator. 
 Addressing this shortcoming is part of planned 1.7.0 improvements.

Original comment by James.Mo...@gmail.com on 5 Jul 2014 at 3:56

[GoogleCodeExporter]

Oh I see, thank you!  Yes I confirm I was able to create a repo in a specific 
project (when logged as admin.

Thank you for your help (and your work on Gitblit)!

Original comment by fgeorges on 6 Jul 2014 at 2:16