Restarting issue when overriding configs

billcolumbia

Overall it's pretty straight forward from a UI perspective. I think the docs could hand hold though for the times that people or need it, or for the people that learn best with detailed instructions and imitating before going on their own. Nice work!

The only misbehaving I'm seeing is when I override configs, Indigo notices and asks to stop or restart the stack. Sometimes when I press restart, it does, but then asks the same question seemingly infinitely until I stop the stack. Close the app and start it back up.

Indigo

billcolumbia when I override configs, Indigo notices and asks to stop or restart the stack. Sometimes when I press restart, it does, but then asks the same question seemingly infinitely until I stop the stack

Fortuitously I experienced this cycle myself tonight. I was able to trace through why it happened and it's because Apple's FSEvents system is reporting spurious filesystem changes that simply aren't happening. I've observed this for some time, and previously added debouncing and the like in an attempt to work around it, but those efforts have proven insufficient as you discovered. So I've just implemented a fingerprinting mechanism that will determine whether the FS actually changed. It's fixed the issue for me, so I'm hoping this is sorted once and for all.

This will be in the next release.

Indigo

Hey Bill, thanks for your first-run feedback, it's really valuable. I have previously made an initial attempt at this kind of document at https://indigostack.app/docs/getting-started/the-basics/ Do you think a followup page to that might be useful — perhaps an explicit step-by-step tutorial to get, say, Drupal up and running?

Sorry to hear about the config override issue you've experienced. I've not seen this myself; have you been able to reliably replicate this at all? I assume you're talking about editing/providing config overrides directly at the filesystem (rather than the PHP config overrides in the GUI)? Anything particular in that line of thinking that you think might be a trigger? If you could build a stack that makes this happen and send it to me at hello@indigostack.app I'd love to try it.

billcolumbia

Indigo Hey Bill, thanks for your first-run feedback, it's really valuable. I have previously made an initial attempt at this kind of document at https://indigostack.app/docs/getting-started/the-basics/ Do you think a followup page to that might be useful — perhaps an explicit step-by-step tutorial to get, say, Drupal up and running?

I don't thinks its necessary but could be nice icing!

Indigo Sorry to hear about the config override issue you've experienced. I've not seen this myself; have you been able to reliably replicate this at all? I assume you're talking about editing/providing config overrides directly at the filesystem (rather than the PHP config overrides in the GUI)? Anything particular in that line of thinking that you think might be a trigger? If you could build a stack that makes this happen and send it to me at [hello@indigostack.app](mailto:hello@indigostack.app) I'd love to try it.

I just emailed you my stack that does it. I just edited some conf files and it would do it 2-4 times after making one save while the stack was up. It didn't do it as many times in a row as I ran into yesterday though.

Indigo

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 zzz-overrides.ini file
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:

~/Library/Logs/com.marmaladesoul.Indigo
/var/log/com.marmaladesoul.IndigoHelper

Thanks for your ongoing help seeing if we can resolve this 🙂

billcolumbia

Indigo 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)

Not that I'm seeing. 🤔

Indigo 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)

Nope

Indigo is your indigostack file perhaps being version controlled with something non-git eg SVN, Mercurial or something? (I haven't tested this)

Nope

Indigo 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

VS Code

Indigo are you editing the existing config files, or are you dragging in / creating new ones? If the latter, what exactly?

Originally I had some confusion about what to edit, but as of right now I've been copying the files from ~/.indigo to my stack then editing them once in the stack (usually while the stack is down). Maybe I recreate my same stack fresh and make sure I didn't gum it up with something while learning that process?

For what it's worth the issue is super minor for me. It's really easy to quit and restart the app.

billcolumbia

Well I feel a little less crazy now! Thanks for the update!