akephalos icon indicating copy to clipboard operation
akephalos copied to clipboard

Akephalos on Windows

Open bernerdschaefer opened this issue 14 years ago • 5 comments

There are two issues that I know of preventing akephalos from running on windows:

  1. fork() This is only used in RemoteClient when firing up the server. It appears that IO.popen() should work just fine instead of fork/exec.

  2. unix sockets For speed reasons, akephalos uses unix sockets for DRb communications. There should be a way to specify whether you want to use unix sockets or TCP sockets (and do so automatically on windows)

(Requested by @samus)

bernerdschaefer avatar Sep 14 '10 00:09 bernerdschaefer

I have now removed fork/exec and unix domain sockets from akephalos (bbeb728). Can you test against master and let me know if you can get any farther?

bernerdschaefer avatar Sep 22 '10 19:09 bernerdschaefer

I pulled the source and tried running the specs on windows under MRI 1.8.7

I got this error: http://gist.github.com/640510

So I tried patching line 41 of lib/remote_client.rb to include ruby in the command:

bin_path = Akephalos::BIN_DIR + 'akephalos'
remote_client = IO.popen("ruby #{bin_path} #{port}")

And then I got this error:

http://gist.github.com/640513

mattwynne avatar Oct 22 '10 13:10 mattwynne

I now have a windows VM instance, so I'll be taking a look into these windows issues soon.

bernerdschaefer avatar Nov 24 '10 21:11 bernerdschaefer

Thanks ... akephalos represents pretty much the only hope of running capybara and cucumber on windows :)

spacefugitive avatar Nov 29 '10 05:11 spacefugitive

I just opened a pull request that should fix the remaining issue mentioned by mattwynne: https://github.com/bernerdschaefer/akephalos/pull/53

noniq avatar Feb 14 '11 12:02 noniq