The first time a user encounters the "create a repo" or "use an existing one" flow is when installing the observability stack. First, the repos are organized by stack IP, which may not be ideal when selecting older checked out repos which may or may not have the same IP. We need a mechanism that's not tied to an IP.
Second, the UX is clunky. I can't paste the repo in "Use an existing local checkout". ctrl+v doesn't work. This screen should potentially show existing checked out repos in the ~/.config/servestead/repositories folder as that is the default place.
The first time a user encounters the "create a repo" or "use an existing one" flow is when installing the observability stack. First, the repos are organized by stack IP, which may not be ideal when selecting older checked out repos which may or may not have the same IP. We need a mechanism that's not tied to an IP.
Second, the UX is clunky. I can't paste the repo in "Use an existing local checkout". ctrl+v doesn't work. This screen should potentially show existing checked out repos in the ~/.config/servestead/repositories folder as that is the default place.