Hello @billziss-gh,

Beyond not having explicit Gitlab support yet, is there any possibility to use hubs with a Gitlab Free server hosted on premise?

🙏Thanks for developing this useful software and making it accessible to the community.

Regards,
Claudio Salvio

Hello @billziss-gh ,

As an initial test, I installed the "HUBFS 2022 Beta1" (hubfs-win-1.0.22067.msi) and was able to connect to my Github Repo as it shows.

For a second step, I have been able to compile HUBFS in my MSYS2/Mingw x64 to produce the hubfs.exe file.

Now I would like to start up the hubfs.exe in a command prompt with the proper steps to connect to my repo again instead of using the "net use H: ..." command this time to validate that the build was successful.

Can you please show me the CLI options needed to make this work?

Basically, I would like to know what the CLI options that are being used when done with "net use".

Thanks

I have a private repo on my account and orgs, shared with other users.

When I use HUBFS, (on Windows, installed with .msi, authenticated with "Preform GitHub Auth") I can access my private repos without any issue. All features that I've tested work as expected.

However, if I try to access a private repo owned by a different user or org, even if I'm the owner of the org, I cannot access them.

They also do not show up in the top level user's (or org's) folder(s).

If I try to go to the project's URL directly, I get a "Windows cannot access" error with code: 0x80004005 that looks identical to what you see when you access a nonexistent repo:

Nice initiative 👏
I had a look at your source code and just wanted to confirm and highlight that your "ref" seems to only handle refs/heads/*, refs/tags/* and hashes.
Except there can be other refs. git notes command and https://github.com/google/git-appraise store content under refs/notes, etc.

When I try to run hubfs I get the following error

{23:39}~ ➭ hubfs /mnt
hubfs: client error: Device Flow must be explicitly enabled for this App (device_flow_disabled)

I suspect this is due to the recent github change which means that GitHub now requires device flow to be enabled for apps rather than having it enabled by default and the hubfs app does not yet have this enabled.

Update: a workaround in the meantime could be to use the -auth option to specify a different way of authenticating with GitHub. hubfs -auth optional /mnt, for example, doesn't give this error

In this commit, WinFsp was changed from AGPL to GPL. I wonder if the same could be done for HUBFS. Many companies outright forbid the use of AGPL software in any capacity.

I think this is a very promising project, and I would like to contribute to it, but we cannot proceed with it under the AGPL.

I just found hubfs, and it seems promising to help people not normally using git... but I'm not sure it would work in my use-case, and I can't find any docs about it.

We are utilizing an old program that makes hundreds of data-files while operation are ongoing. All of these data-files are somehow linked together, and if just one of the data-files are not of the current version the program crashes. :-( If the program is shut down correctly, then we know all files are valid.

For this reason, I'm unsure if hubfs would be compatible with it, as I'm unsure about when exactly files are committed to the repository.

So my questions are:

1. Are each change to a file triggering a commit of that file?
2. If not, then are a number of file-changes within a time-period triggering a commit of those files?
3. Would it be possible to somehow only trigger a commit of all changed files when we know it's safe to do so?

Thank you!

Hi!

I've followed all the steps to setup HubFS

• Authenticated using the browser
  

• Mounted the drive
  

But I see nothing inside.

Using Windows 11 and the latest version of WinFsp.

As the title, it keeps me reauthorized every time I run the command.
I found out that it doesn't rewrite the authentication key to the default key which is usually at ~/.local/share/keyrings (checked the timestamp, nothing changed)

Debug message does not contain any useful information in this case..

Hello,

I was looking at the HUBFS as it might be what I need to use to learn from as a template to build out the unionized ssh type filesystem and was reviewing the code in the src/fs section of hubfs.

https://github.com/winfsp/hubfs/tree/master/src/fs

What is interesting is that the hubfs seems to utilize:

memfs
nullfs
overlayfs
port
ptfs (passthrough)
unionfs

I was wondering if all of these are really used together.

Can you please elaborate more on how this works together since I would estimate that the "nullfs" is started initially until the user maps into github and then, just perhaps the unionfs is used to combine the different repositories that are under any given singe organization, or something along those lines.

Can you please help me understand the flow of things since as you know, I am interested in something similar, but to union mappings to different user accounts on separate ssh servers into a single R/W directory structure mounted.

Any information that you could provide would be greatly appreciated.

Happy Holidays and I look forward to hearing back from you.
Thanks

On:

• Ubuntu 18.04

I've followed the instructions in the README and managed to mount a Github private repository , authorizing my Ubuntu PC via the one-time code.

I mount and then create / write top level files in the repo :

$ hubfs ~/mnt/
<... use one-time code and launch browser to authorize device aka PC ... >
$ # in another terminal ... :
$ cd ~/mnt/d-w-moore2/practice/master ; touch a ; vim README.md # make changes and save
$ cd ~ ; fusermount -u mnt

Then:

• I do not notice Github in the browser showing any commits on master to reflect the touched a file and README.md changes.
• re-mounting and cd'ing into the directory again, I can confirm the changes have not been saved

This seems like an interesting product but it would be great if the readme explained more of how changes are handled.
For example, if you change a file, is it then possible to commit that change?