search

pantheon-systems / localdev-issues

Issue tracking for Pantheon localdev
6 stars 2 forks source link

Localdev stalls and not responding when account is binded to several organizations #90

Open dqlopez opened 3 years ago

dqlopez commented 3 years ago

When an account is associated with several organizations and have lots of sites (org and site level), the Localdev ends up in WSOD after attempting to clone the sites. From my assumption, it seems that by default it is cloning all the sites within the organization associated with the account. De-associating the account with the said organization or reducing the site under the account seems to address the issue. It would be best to have an option on initial startup on which organizations/site level the Localdev would pull the sites.

pirog commented 2 years ago

We do not have a great way to handle accounts with a LARGE amount of sites. Some top of mind options to handle this in order of increasing difficulty:

  1. Localdev is intended primarily for individuals and smaller orgs/agencies so limit its usage to users with only a single org and less than a few hundred projects. For people with more, recommend lando.
  2. Only add sites that users have DIRECT access too, eg not through organizational relationships
  3. Set a low upper bound for initial amount of sites (like 25?) and during setup let the user select the sites they want to add. Then in the main dashboard allow the user to add more sites using similar UX and to their hearts content.