5
Wanted: A "stop site gracefully" option when stuck on Provisioning...
J
Jeff Safire
It would be a great to have an option for "Stop site gracefully" akin to apachectl. When I need to have 2 sites running to compare code for debugging, the second site often gets stuck on Provisioning. Interestingly, I decided to write this feature request post this morning because I had two sites running fine last night while debugging. But, this morning when I opened my MacBook, the second one was Provisioning... - endlessly. Perplexing why it was provisioning after it was running fine for several hours. Yes, my MB did go to sleep overnight, but that shouldn't cause this. The only way to stop that is to stop the first site and then quit Local. But, it's always a wincer when quitting while a site is provisioning or otherwise active in some way, with fingers crossed nothing gets corrupted. A graceful-stop or force-stop would be much welcome.
Local 5.5.3 / Safari 13.1.1 / OS X 10.14.6 / MB Pro, 16 GB
NdnaJnz
Activity
Benjamin Turner
When you ended up quitting and restarting Local, was the site still working, for example, when you started the site again, were you able to access it from a browser?
Typically when I've seen Local stuck at provisioning, that's been because the UI can't proceed because _something_ didn't respond correctly or within a given timeout.
That may be due to something like Local is asking for elevated priviledges to start MySQL but never gets that permission.
In your mind, what would you expect Local to do if it gets into that state -- clean things up for you or just let you know that something isn't quite right?
J
Jeff Safire
@Benjamin Turner: A message stating WHAT isn't right – not just that
something
isn't right. Many of us here are developers, not just website designer-builders. Devs want to know what the actual problem is, as they are often able to fix the problem on their own. But, with issues like this hidden under the Local front end, that's usually not possible. A popup message listing the problem is a good start; then perhaps offer to either force-stop the affected site, or carefully
quit Local. Or maybe a combination that includes stopping any running sites, and then Restart Local.Thanks for the reply!
Jeff
Benjamin Turner
@Jeff Safire: I definitely understand wanting to know what the error is.
For what it's worth, there's often a lot of information that's logged to the Local log which you can open by clicking on "Help > Reveal Local's Log" or by navigating directly using the instructions here:
- https://localbyflywheel.com/community/t/how-do-i-retrieve-locals-log-file/3720