Thanks for emailing through your stack. Weirdly it behaves just fine in my testing. I did this:
- Added the stack to Indigo and started it up.
- with it running, I opened the
stack.indigostack file bundle in Panic Nova and added a comment to the end of the PHP
- when I hit save in Nova, a second or two later Indigo would throw up a dialog with "The stack 'Craft Test' has changed on disk."; when I click "restart stack" everything just worked as expected and nothing further happened.
I made changes as above ten times and didn't see the issue even once.
I don't really have any great ideas from this point, but here's what I'm wondering:
- could there be some unexpected hidden files in your indigostack file bundle? (cmd-shift-fullstop to show them) (there's none in the file you sent me)
- is your indigostack file perhaps being synced with Dropbox or Syncthing, or something? (I use these and haven't seen an issue, but worth checking)
- is your indigostack file perhaps being version controlled with something non-git eg SVN, Mercurial or something? (I haven't tested this)
- are you using an unusual means of editing the config files externally? (I regularly use Nova, VS Code, Sublime and git to externally change the content of my Indigo stack files and have not seen any issues).
- are you editing the existing config files, or are you dragging in / creating new ones? If the latter, what exactly?
There's one final thing I might ask of you, which is to send me your log files. Indigo creates a fresh logfile on each launch, so please quit it, restart it, take steps to recreate the problem, then quit Indigo without doing anything else.
Then grab the latest log file from each of:
Thanks for your ongoing help seeing if we can resolve this 🙂