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.

Sign up for GitHub

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

Jump to bottom

Prevent need to move device.yml onto the device #153

Open
joepavitt opened this issue Jul 27, 2023 · 0 comments
Open

Prevent need to move device.yml onto the device #153

joepavitt opened this issue Jul 27, 2023 · 0 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Jul 27, 2023 •
edited
Loading

Description

As part of the Device UX Review I had highlighted that a pain point in the onboarding of a new device is actually the moving of the yml file from wherever your FF instance is running and getting it onto your device.

A much cleaner process here would be to be able to run commands directly from the device agent, pseudo example as follows:

flowforge-device-agent login
flowforge-device-agent connect <some-unique-token>

Following which the connect command would pull the yml and place it accordingly such that the device agent would work.
@joepavitt joepavitt added needs-triage Needs looking at to decide what to do feature-request New feature or request that needs to be turned into Epic/Story details labels Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
☁️ Product Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joepavitt