Windows support about overcast HOT 8 CLOSED

Decided to check it in in case I felt like hacking on it this weekend:

jdiamond@e3549bd

I can init, create a droplet, and run scripts on it so far.

from overcast.

Whoa, nice work! The thing is, Windows support isn't something I'll be able to maintain, so the idea of being on the hook for code I can't easily test, or the "Why isn't this working on my Windows machine?" questions that I won't be able to answer, doesn't sound great. I think official support should stay limited to OS X/Linux for now so I can be confident that Overcast does what it says on the tin. How about if in the README I link to your fork for "experimental" Windows support for now?

from overcast.

Totally understand. I was actually thinking about it during my drive home and I think I can remove the Windows-isms. I'll play with it a bit and get back to you.

from overcast.

I was able to get as far as deploying overcast-charts. Even though the changes required to get it to work are pretty minor, I'm not sure it's worth submitting yet so closing this for now.

If anybody wants to check it out, branch is here:

https://github.com/jdiamond/overcast/tree/windows-support

from overcast.

There's always ssh2 for cross platform, non-child process-based ssh/sftp capabilities :-)

from overcast.

That's really interesting.

The problem is actually executing scripts and commands on the local machine. Overcast spawns ssh, scp, ssh-keygen, bash, mkdir, and chmod.

Maybe ssh2, scp2, ssh-keygen2, and ShellJS could replace spawning processes locally.

(Except ssh-keygen2 is just a wrapper around ssh-keygen so that would still have to be in the PATH.)

from overcast.

@jdiamond: I changed my mind. Even though I don't want to officially support Windows, I can still use your code to make Overcast more Windows-friendly. I've created a PR using your code: #10. Take a look and let me know what you think.

from overcast.

Wow, very cool! I will test it out tomorrow at work.

from overcast.