Spin up IPFS as part of the CLI's dev command

[avivash]

Boris and I were chatting about installing/starting the IPFS daemon as part of the CLI for now, since we will be using IPFS for at least a little bit longer and it's the only thing we don't currently do for the user

[bmann]

Thanks @avivash -- yeah, we may as well, then it's the one path install route. In case it's useful to look at what the original CLI does --> https://github.com/fission-codes/fission/tree/main/fission-cli

[avivash]

nice, thanks!

[avivash]

I've added this now and I think I've caught most of the edge cases, but I haven't tested on Windows yet... it should still work on Windows, but the one issue that might happen on Windows is if the user already has IPFS running then they try to change the IPFS port when starting up the EveryCLI(this should still work on Mac and Linux though)

[avivash]

Okay, I've added a workaround that should handle the situation I described above in Windows. The only thing is I don't have a way to test it 😅

[bmann]

Sweet, Andy! How can I test a run through on Mac?

[avivash]

Sweet, Andy! How can I test a run through on Mac?

you'll just need to update the CLI, start it up and it will spin up IPFS for you.

if you have IPFS running somewhere else already, it will stop that instance automatically because it needs to add either the IPFS port from EveryCLI's default homestar.toml or the one specified in your custom --config arg into the IPFS config before spinning it up. That was a long-winded explanation 😅, but the short answer is it should just work if you update the CLI and run the every dev <function_path> command. It should work regardless of whether you've already installed IPFS on your machine before too. I'd like to do some testing on windows if possible though, because i'm not sure if the command i wrote to kill the existing process will work on windows yet