Okay so I have a weird situation:
I unpacked a zip-file. It was 180 MB and the unpacked folder had 9 GB. Immediately after unpacking, Indigo notified me, that the stack files on disk changed, and it had to restart them. After confirming, it got stuck on waiting for nginx. I restarted indigo a few times without success, until finally all my stacks (3 in total) were gone.
I had this problem already a few weeks ago and ended up setting up my stacks (and mysql db including tables and stuff 🥲) from scratch. But while researching last time I stumbled across somebody, that found his stack files in his trash.
So this time I looked in the trash, too - and found two of my stack folders in there. Somehow they got "automatically" deleted. Furthermore, macOS did not offer the "put back" option in the context menu. It seems, the original path was not put into the ds_store file, so macOS did not know, where the folders came from.
I was able to restore my stacks and data by:
- go to the documents folder where the "stack X.indigostack" files are and open them, so they would reappear in the indigo window
- drag&drop the stack folders from the trash to userfolder/.indigo/stacks
- restart the stacks
I'm not quite sure what caused this behaviour. My first guess was that the storage-optimization caused some indigo-files to be removed from disk (e.g. in the documents folder, that are synced with iCloud) and somehow indigo "panicked" and deleted the stack folders of the stackfiles, that "changed".
A con argument is, that i still have 120 of 500 GB free on my disk. But who knows, how macOS handles the storage optimization.
Long story short - maybe you are able to fix/prevent behaviour like this 🙂
