I am working on a development site while I am still learning Local. I work on this site from 3 different locations: my office terminal, home office terminal, and from my laptop when I am on the road. I pull the site from the server, make my edits, then I push the edits back to the server. I have 2 questions:
Is this the best practice for my use case? Is there better/simpler way to do this when potentially working on 3 different machines to develop one site?
I don’t know that I completely under the “Stop Site” feature in Local. What I have been doing is starting the site, making my edits, pushing the edits, then stopping the site when I log out of Local. Is it necessary to stopping the site each time I finish work at a terminal? If my site was a live production site, I could see this as a good “kill switch” use, if I had to take the site down quickly. But, in the case of a development site (and I only have one site that I am working on in Local), what is the logical way to use this feature? I did a search in Help Docs, the community, and Google, but I didn’t find anything that addressed this specific question.
No issue to be resolved. Just need an answer to a question.
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.