G-Node / G-Node/gogs

Initial impressions/questions: Default FAQ, ssh urls,

Open
#14 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
16
Forks
15
PR merge metrics
No merged PRs in 30d

Description

I am going through the https://web.gin.g-node.org/G-Node/Info/wiki/InHouseWithoutDocker . Thank you for the nice documentation -- it seems has worked out for me quite splendidly! Here I want to outline a few points which I have observed and which you might (or might not) want to address or just explain (decided not to separate into separate issues for now, added empty checkboxes to signal "something to address"). Some issues might relate more to upstream gogs .

- [ ] There is **no default FAQ** page (http://localhost:3000/G-Node/Info/wiki/FaqTroubleshooting gives 404 page)
- [ ] **no options to initialize git-annex while creating a repo** In above FAQ I was hoping to find on how to initialize "git annex" repository. I could not find an obvious setting somewhere while initializing a new repo or after to invoke "git annex init" on the server side. If such settings group existed (during creation) would be nice to be able to state desired backend for the annex (e.g. MD5) to partially mitigate those [problems under windows](https://web.gin.g-node.org/G-Node/Info/wiki/SomeNotesOnGitAnnex#the-problem). E.g. in datalad, by default, we just now use md5 backend:
```shell
$> datalad create /tmp/test; cat /tmp/test/.gitattributes
[INFO ] Creating a new annex repo at /tmp/test
create(ok): /tmp/test (dataset)
* annex.backend=MD5E
```
which should be sufficient for any scientific needs.
- [ ] **incomplete ssh urls** I have configured to not use builtin ssh. ssh urls provided by web interface "aren't complete" and rely on ssh account having entering the shell at the level of `~/gogs-repositories`. I guess, whenever no internal ssh server is configured, I guess ssh urls need to be adjusted to reflect that . Anyways, I guess I better need to try the deployment with builtin ssh server, since I guess otherwise no multiple users would be able to push data
- [ ] **http://... does not support git-annex** I "git annex init"ed server side repo by adding an ssh remote, and letting git annex sync to init it, which doesn't work since
```
[Macaron] 2018-01-23 11:15:16: Started GET /yarikoptic/test1.git/config for [::1]
[Macaron] 2018-01-23 11:15:16: Completed GET /yarikoptic/test1.git/config 404 Not Found in 4.42299ms
```
i.e. git-annex trying to access that `/config` but it is not "interfaced" by the http/web interface. I wondered if it might become sufficient to make `/config` provided for git-annex so it could deduce uuid of that remote repo and request content straight via http?

I guess some of those issues are addressed via custom handling in `gin` cmdline client, but I thought it might be nice if GIN could work via native "git-annex" commands

If no objections, I will keep adding notes here as I go along. And please take those above points not as a critic of some kind, and just as my humble attempt on feedback to make GIN even better ;)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.