Skip to content
This repository has been archived by the owner on May 28, 2023. It is now read-only.

WIP (windows support): stub for supporting windows via fsnotify.v1 #6

Closed
wants to merge 2 commits into from

Conversation

blaggacao
Copy link

No idea, if this works, nor how to build it, so far. But it is a starting point to the best of my knowledge. I would be pleased about some sort of collaboration in order to get this badly needed docker-rsync working on windows...

@blaggacao
Copy link
Author

Feels good, it built successfully! 💃

@blaggacao
Copy link
Author

To last commit: I didn't find a more elegant way to avoid this. Maybe this "external dependency" can be removed completely, although a basic one?

@mattes
Copy link
Contributor

mattes commented Oct 5, 2015

Thanks, @blaggacao for your PR. I don't want to duplicate main.go. I think we should look at watch.go. I will have a look into this later this week.

@mattes mattes mentioned this pull request Oct 5, 2015
@blaggacao
Copy link
Author

Actually, I found watch.go to be the part that is taken care of by fsnotify. An alternative is to make a wrapper around fsnotify in order to adhere to the watch.go signature. However, this would be a wrapper around a wrapper. Until fsevents gets merged into fsnotify, this would be temporary anyhow...

However, I think fsnotify project misses some traction atm.

fmt.Printf("Syncing %s (local) to %s (docker-machine %s)\n", *srcpath, *dstpath, machineName)
Sync(machineName, port, rpath, rpathDir, *verbose) // initial sync

if *watch {
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This if statement is the only differing part. I also was not pleased to duplicate whole main.go - Maybe there could be a small wrapper around the actual (darwin) watch.go, which imitates fsnotify.v1 signature?

@duro
Copy link

duro commented Feb 4, 2016

Hey @blaggacao and @mattes, any progress on this? I have been using this library with great success on my OS X machine, but I am about to start a new project with a team where some of the engineers use Windows.

Seems like you guys are close, and I'd love to be able to make this library part of the tooling for this new project as well.

@blaggacao
Copy link
Author

@duro I'm afraid, I'm out, as this is no longer a priority for me.

@duro
Copy link

duro commented Feb 4, 2016

@blaggacao did you go a different route?

@blaggacao
Copy link
Author

Well I'm betting on docker-machine to leverage the docker volume plugin to setup a net protocol file share or an rsync volume.

So syncing would be handled by docker.
And mounting would be handled by a docker-machine share.

I've seen a proposal, but has no very high prio, I think.

@enmand
Copy link
Contributor

enmand commented Feb 8, 2016

I've added support for Windows in #13.

-Dan

@mattes
Copy link
Contributor

mattes commented Apr 19, 2016

Closing in favor of #13

@mattes mattes closed this Apr 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants