Option to generate config for running FireFly core outside docker compose about firefly-cli HOT 3 CLOSED

While not exactly a duplicate of #2, there is a lot of overlap here. It's a good idea.

from firefly-cli.

@peterbroadhurst How do you think node/org registration should work in this case? I'm guessing running the firefly node outside docker will be a manual command because the CLI won't know where the firefly binary is that you want to run (and you may need to recompile/rerun many times during testing). When running in this mode, should we just skip the registration portion of runFirstTimeSetup()?

from firefly-cli.

Great point... I guess with the manual process today we let everything init first then do the manual editing on the yaml.

So we could definitely just skip the registration step, but then you've still got manual stuff to do, so I'm wondering if we've made things better.
Or we could have a separate command to re-write the config as external, after you've done the initial ff start (not sure what that command would be though(.
Or we could decide it's not worth doing anything right now, and the process as it is today isn't too bad, and we could be in danger of over complicating the ff tool for something outside it's core purpose 🤷

from firefly-cli.