can we install it in windows?

[mohamadiarch]

can we install it in windows? which version?

[dkumor]

Unfortunately, windows is not supported right now. Since heedy plugins communicate using Unix sockets and heedy itself sends signals to plug-in processes, windows support would need to wait until Python has Unix socket support on windows, and would require special code to get windows support for controlling windows processes. I am not currently planning to test support until the Unix socket issue is resolved in Python.

[SpongebobSquamirez]

What if you use "bash on ubuntu on windows?" Should that work?

[dkumor]

As far as I know, using WSL (the windows ubuntu) should "just work" with the Linux version of heedy. If you end up trying it, let me know if it works!

[goatlady]

I've managed to get it working in WSL2 (running the default Ubuntu) on Windows 11.

The downloadable file didn't work for me (could have been some user error in there), but building it and then running it did work.

Steps (all performed from the WSL terminal):

1. update Go to the latest version - I had to use the which go command to find the location of the older version that was still lurking after following the instructions in the linked article for removing old versions
2. update node.js and npm to the latest versions
3. follow the readme instructions for building the release version
4. follow the readme instructions for running heedy

I got two warnings: No supported Python interpreter found & The public is not allowed to access event websockets but the app seems to be running so no doubt I'll figure those out next.

[dkumor]

It's great that you manged to get it working in WSL2! One quick comment: please make sure to build off the release tag, since master is currently not fully functional!

Here's why the errors you mentioned happen:

1. No supported Python interpreter - Python 3.7 is required and must have pip and venv support installed. Heedy checks for this when creating a database, and if it doesn't find the above, it leaves Python support turned off. It can be set up after database creation by setting the python plugin's path in heedy.conf.
2. The public is not allowed to access event websockets - this is working as expected - heedy is configured so that only logged in users can access the websocket that streams events. This is used from the web interface to keep everything live. When visiting the heedy page before logging in, the web app tries to connect to the websocket and gets this error. It then stops connecting and waits for you to log in!

I am curious why the pre-built version doesn't work, however - do you have any information as to the error that happened when trying to run?