please keep git sync

[LCLLL]

Git sync is a very good function. It can save user data and complete collaboration in small teams. The most important thing is that the ownership of git belongs to the user, so data security is guaranteed. I think it is in line with what you said "local and privacy-focused" .

[archywillhe]

Good point; just a quick question: does your team use git in CLI a lot? (or prefer using git via a GUI like VSCode or Github Desktop?)

I haven't dived into the code regards to Kong's implementation of git-sync. My plan now is to allow users to select an existing git repo as Insomnium Workspace, where a .insomnium/ folder will be created. And users can then git sync this folder via CLI, Vscode, Github, etc.

Or would you prefer an existing GUI in Insomnium that settles the git-sync entirely (so CLI or other apps are not needed?) i.e. so more none-programmers-friendly (which makes good sense if your team has none-coder, etc, that are also testing with Insomnium).

Would be nice if you can elaborate more on how you would imagine your team using git-sync in Insomnium, etc; thanks! (Or was git-sync previously a free feature in the older version of Insomnia?)

[archywillhe]

aw I think I know what you mean; I will be looking more into Insomnia codebase these few days
I think I should be able to roll it back in Insomnium v0.2~v0.3. I will update this thread when it's out

[jeanchristopheMICHEL]

With 0.2.1.b is more easy to pull down a git project and is very nice !! As LCLLL say, we can do Git operation with some other programs, but I hope Git sync go back to GUI, is more confortable. For your roadmap, you may also include a popup warning when actual branch is not up to date.

[trevorgehman]

Yeah I think having the ability to sync in the GUI with a Github repository would be awesome. Would make working with teams so much simpler.

[archywillhe]

good points; thanks guy

[steenbag]

I think just using the GUI as the mechanism to edit the files, and then leaving the git part to external tools would be the best approach.

• Users already have preferred git workflows/tooling. There are tons of GUIs for Git available for non-technical folks.
• Removes complexity of having to deal with branching conflicts in the UI.

[ivanrusanov]

Hello everyone! I'm not sure that I understand you right. Do you mean that Insomnium can save my API requests into special directory which can be managed by git? Where this directory is? Can I initialise git repository there? Does Insomnium store requests as plain text files so I can merge changes in case of conflicts? Thank you in advance.

[archywillhe]

oh yeah that will be an upcoming feature; I'm still working on it (you can find related discussion on discord)

[archywillhe]

The UI is back. I'll be making more improvements along the way as we transition to be file-system-oriented

[yurikus]

I would like join in support of git sync. I just tried to add git repo hosted over git:// and http:// protocols and neither worked. git:// was refused outright with "unrecognized scheme", http:// failed with a couple of errors:

• first "Error invoking remote method 'axiosRequest': Error: connect ECONNREFUSED ::1:58080", note ::1 - server is only listening on IPv4 not on IPv6. This error appears first time clicking on the collection.
• second of which is "Could not find HEAD". I tried git --daemon and mongoose to host the repos. This error appears second time clicking on the colleciton

Issues

• remove requirement for auth token.
• validate git upon clicking on sync
• support http:://, git:// and file://

[archywillhe]

hi yurikus thanks for the comment. the current implementation uses isomorphic-git, which doesn't support git://

A major update is on the way where I'm making file-system first-class citizen so git can be used directly in the cmd which will support all protocols.

[archywillhe]

The isomorphic-git implementation inherited from Insomnia was the reason why git-auth-token was necessary. In the newer version, the use of git-auth-token will be optional.

[yurikus]

Sounds good, thanks

[paulius-valiunas]

I think the "git sync" has to go away. Just let us open a file directly (without manually importing and exporting it to sync changes) and we can use our existing git clients to do the synchronization. That way we don't need to have a separate repository following insomnium's directory structure, we don't need to put up with having little to no control over when and how insomnium commits and pushes changes, we can incorporate insomnium files into the normal product repository and pull requests etc. The "git sync" was only implemented that way to prevent people from using whatever existing sync solutions they had and to force them into buying subscriptions.

[yurikus]

That is indeed a better solution, following the OSS spirit

[ansghof]

I have no idea how Insomnium syncs collections to git. The problem is that as soon as I get a conflict, Insomnium's built-in git tools just give up and tell me to fix the problems otherwise. I then tried to locate the local .git folder which took me a lot of time. I can't find it at the application's data folder or anywhere where it would logically belong. The easiest thing would be to have a collection folder somewhere on the filesystem (preferrably within my code project of which I'd like to test the APIs) and use git from there.

If the tool hides all git related things from me but isn't able to solve simple git tasks, then rather don't add it to the tool or offer an alternative way of just handling git via command line.

Maybe I'm just too stupid but I'm unable to locate where Insomnium is saving my collection's git files. If anyone could point me to the folder on MacOS, I'd be happy to just do git in the terminal.

[athrunsun]

Hey guys, if I want to sync all the data to a git repo other than git providers provided by Insomnium, which folder should I care about? Specifically on macOS, is it ~/Library/Application Support/Insomnium?