-
Notifications
You must be signed in to change notification settings - Fork 116
Make Orbit work on Windows #159
Comments
I'd like to try to do something to get orbit on windows. People I'd like to use orbit with use windows. But perhaps we should wait for #192 to complete before I dive into this... I'm not sure what the shell files are doing right now and whether the go-ipfs dist in orbit is working for windows or not. I'll try to get a better understanding. |
@theobat you could give it a try and try to run it on windows from master. In theory it should work but I've never tested it. |
I tried a few weeks ago, only problem was the shell scripts are not executable on traditional windows machines: Perhaps we could try to translate these in node scripts ? |
The shell scripts are not run anymore (need to remove from the repo). I updated everything today including possible working version for Windows. |
so first of all we get this :
Which is minor cause removing the log= and the ipfs option solve the problem. But then, we get a slightly different issue that I remember having solved, when we try to connect with a username I get this error:
I'm pretty sure I was creating the directory if it did not exist you think it's not the app's responsibility to do such thing ? After creating the dir, next error is a right issue on node_module which is probably how I handled install... Will investigate more later |
Thanks for the investigations. It seems env variables indeed are a problem in Windows :/ Need to find a good solution for that. Re. the directory, IPFS should create the data directory by itself. I might've touched the orbit data dir creation code as I figured it's not needed, but perhaps it is after all. If I did, feel free to put it back in, it was removed shortsightedly. |
Just as a follow up I managed to make it "work" without the env variable and with a hand created directory, but I didn't seem to get any peer.. Will try to investigate later. |
Orbit (Electron app) should run on Windows.
Ref #158
Ref #144
The text was updated successfully, but these errors were encountered: