Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be able to use EveryCLI to connect to custom subnets or peers #12

Closed
bmann opened this issue Mar 14, 2024 · 0 comments
Closed

Be able to use EveryCLI to connect to custom subnets or peers #12

bmann opened this issue Mar 14, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@bmann
Copy link

bmann commented Mar 14, 2024

I'd like to be able to use EveryCLI to manage my Homestar node but also connect to the Fission Team Subnet.

I thought I could edit the toml file directly in the node_modules folder, but nope!

On startup it writes out the contents of the workflow.toml file in the node_modules folder: https://github.com/everywhere-computer/every-cli/blob/main/src/dev.js (so edits get overwritten)

Other notes: maybe call this homestar.toml or subnets.toml?

I think we can accomplish this with passing in config, e.g. --config /path/to/homestar.toml

Don't know if there is a hard dependency on homestar config settings ipvm-wg/homestar#606 -- feels like with how every works now, this is non-blocking, we can just read in the custom config for now.

@bmann bmann added the enhancement New feature or request label Mar 14, 2024
@avivash avivash self-assigned this Mar 14, 2024
@walkah walkah closed this as completed Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants