-
Notifications
You must be signed in to change notification settings - Fork 3
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
Using old i2cssh config files #1
Comments
Yes it is on the Todo list! I am currently polishing the ec2 intergration . |
so i did some first integrations, clusters should already work. can you check if it's working with your existing file. and do you have any preference on what should work next |
Just tested and it did not like my config file. GUessing its not ignoring the direction and boradcast bits. ---
version: 2
clusters:
direction: row
broadcast: true
sakai-dev:
columns: 3
hosts:
- lmapp0d
- lmapp1d
- lmadmind
appbuild:
hosts:
- appbuild0
- appbuild1 doing |
are you using the latest beta of iterm2? |
latest nightly actually. |
sorry that was my mistake. pushed 1.2.3 to npmjs which is working with your config file. |
seems your changes have not made it to npmjs yet |
should be in by now? one more question on your config. |
can you safely do a screenshot of this? or edit that and make it a code block? not sure i got what that painting means :) |
yeah already did after realizing it wouldnt actually save my ascii art properly lol |
ok got it. will fiddle around should not be to hard to implement. |
Hey so I just stumbled on your re-write and I like it, much simpler and faster than original, but it seems to not be able to use my already existing .i2cssh file :(, my node knowledge is non existent otherwise I would start doing some PRs. Any chance to add that?
The text was updated successfully, but these errors were encountered: