New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial impressions/questions: Default FAQ, ssh urls, #14
Comments
Hey there Let me shortly comment on some of the points: In principle the use of the vanilla gin repo is discouraged for a lab deployment, rather we have a special branch for it (gin@home). That's the one we base the docker upon... It's not mentioned in the without docker documentation and it really should... Regarding deployment and ssh related issues: A lot of it is addressed in the docker build, we have just not written it for the "deploy without docker" yet (hence the tutorial is not linked). We have no annex init option so far, however, it's an interesting idea. We also don't support annex via HTTP currently. It's on my list of things that would be nice, however. |
Thank you @cgars |
Oh, my. Well, it should at least say work in progress then. I guess I'll give it some love later this week, including the steps for ssh direct setup, which are briefly:
currently, the gin@hoime branches start.sh might be a good starting point for an overview... In any case i am glad that the Tutorial it did help to some degree though!
It's basically a cherry-picked version of master, not including the GnodeGin specific things (eg. Links to wikis, legal stuff, functions that require or imply other deployed services etc. ). Simply speaking its a GIN/gogs Server supporting annex and meant for a lab deploy. Thank for checking back and commenting. Ill value the time you invest for it! |
Hi, I'm just starting with data versioning (having been a long time git user for code) and I like what I see in both A big problem I have is to allow both power users and non-technical users collaborate on the same dataset. This is really hard but I hope might be doable with a combination of datalad and gin for each of these user groups respectively. In particular, So, first impression of First impression of Back to Overall I really like these where these projects are going. Thanks for making them. |
@c42f you should also try datalad run whenever you |
Regarding |
Hi Chris, Thanks for reaching out. We very much appreciate the feedback!
This was a big part of the goal for gin-cli and GIN in general. We really want to provide a service that's friendly to the average user without limiting the power user. It's a very common goal for code and data management software and I'm sure we've all seen hundreds of examples of projects trying to strike this balance, to varying degrees of success. I've come to greatly appreciate the difficulty of this a lot more than I used to.
We recently had a GUI frontend developed for Windows that has yet to see a proper release. It supports the core operations (clone, push, pull) which is what we wanted for an initial release. It's in a state where we need to test it more thoroughly before sending it out into the world. https://github.com/G-Node/GinUI If you're considering a cross-platform or Linux GUI, let us know how you're thinking about it. I don't want to promise too much, but there's a plan in place to split out a lot of the internals of gin-cli into a client library which more projects can use. Even in the current state however, the gin-cli is mostly written to accommodate this and I've been planning to look into exporting these internals for use in C code, so something like a GUI can just be built as a shell around the gin-cli internals (instead of shelling out for instance). If you were to start thinking about this, I'd certainly see if I could move this plan ahead a bit faster.
That's great to hear. Thanks!
We haven't considered
Thanks again for checking it out and all the feedback and comments! |
This is great news and exactly what I was looking for. I hadn't thought it through thoroughly, but my thoughts were split between:
Naturally I was expecting to base any GUI work off Anyway, I should check out GinUI, I'm not sure how I missed that. |
It's pretty easy to miss, I guess. We haven't properly announced it yet and it's not mentioned anywhere in the docs. That should be changing soon.
That was part of our original plan as well, but evolved a little differently. GinUI¹ has two parts:
We also considered file browser extensions as you mentioned (Dolphin services and Nautilus scripts, for instance), but other features kept getting higher priority. ¹ I should note that the name of the project might change before it's finally released. Not an important point, but thought you should know since you're checking it out. |
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 .
which should be sufficient for any scientific needs.
~/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 datai.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" commandsIf 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 ;)
The text was updated successfully, but these errors were encountered: