You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the next-video setup there's friction in the step where you need to connect your hosting provider to next-video. We should ultimately have a way to signup/login for a hosting provider and pull in the necessary credentials without having to leave the CLI workflow. The workflow can include a browser window opened by the CLI, which can capture the session/credentials when the login/signup is finished.
Example:
Select from a list of hosting providers
Use the service's oath CLI or open a browser window to the service's login or signup, whichever is most relevant
Capture tokens from the complete workflow (hand wavy, I know, but it has been done. See Fly.io onboarding)
For the Vercel blob workflow I assume could can piggy back on the Vercel CLI oath and not worry about a browser window. I think we can assume if they're going to use Vercel as the app host then they've already signed up for Vercel and just need to log in, and maybe set up Blob for the first time.
For Mux we'll need a special signup workflow built for the CLI browser window. It shouldn't be too complicated to put together, and a quick visual prototype will help communicate the idea.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the
next-video
setup there's friction in the step where you need to connect your hosting provider to next-video. We should ultimately have a way to signup/login for a hosting provider and pull in the necessary credentials without having to leave the CLI workflow. The workflow can include a browser window opened by the CLI, which can capture the session/credentials when the login/signup is finished.Example:
For the Vercel blob workflow I assume could can piggy back on the Vercel CLI oath and not worry about a browser window. I think we can assume if they're going to use Vercel as the app host then they've already signed up for Vercel and just need to log in, and maybe set up Blob for the first time.
For Mux we'll need a special signup workflow built for the CLI browser window. It shouldn't be too complicated to put together, and a quick visual prototype will help communicate the idea.
Beta Was this translation helpful? Give feedback.
All reactions