Empty configuration all of a sudden

nullart

Not exactly sure when this happened, but when I checked the phpmyadmin.test it was not found. Only to find out that in the configuration it is empty. I'm using version 1.0.0-rc.6 (113)

When I checked the trash, I found this deleted entries. How can I put this back?

nullart

Update: I managed to recover the mysql database. I'll put this here as documentation.

moved the folder 7C6E40 from the trash to another my dev folder (see previous post)
in indigo, create a new stack "Server 01" again with the same configuration (in my case: Apache, Mysql 5.7, php 7.4)
Turn On the "Server 01" stack (and let it initialize)
Turn Off the "Server 01" stack
go to ~/.indigo/stacks/<XXXXXX>
delete the files in .indigo/stack/mysql_xxxx_data (just the files in the folder not the folder)
copy the files from mysql_8A4A_data (see previous post) to the mysql_xxxx_data
turn on Server 01 stack

Done. Database recovered.

Hope this helps.

Cheers!

Indigo

Wow, that was some heavy-duty stuff to get things sorted out — glad you were able to get your data back, and thanks for documenting what you did.

Do you have any theories as to what caused this situation? Indigo does move your built stack services to the trash in two circumstances:

when you right-click a stack in Indigo, and choose "Delete..."
when you delete a mystack.indigostack file in the Finder

In both cases the stack's built services folder (7C6E40 in your example) will be in the trash but so will the original stack configuration file, alongside it. So the absence of the stack config file appears to suggest perhaps you (or another Mac app?) moved or deleted the original config file in such a manner that Indigo's filesystem monitor believed it had been deleted.

Another scenario that would result in the behaviour you've seen is if you deleted the original stack file via the terminal (meaning it is deleted immediately, rather than moved to the trash).

I'm curious to know whether you still have the original stack config file (they are stored in ~/Documents/Indigo unless you moved it elsewhere)? If not, that's not something Indigo has caused. If you do though, that's very strange indeed.

nullart

Thank you for the quick response. The stack.indigostack file in documents folder is created today. So, it is confirmed to be deleted and recreated. But, I'm quite sure I didn't delete anything in my documents folder today. Maybe I deleted it unconsciously accidentally.

Ok may I suggest to remove that feature, where indigo deletes the built stacks when the indigo/stack.indigostack is deleted (by accidental or not)? Or maybe move the deletion at the GUI level so it will be a conscious choice to the users/developers?

nullart

Ok I found the issue. The deletion of the file was caused by iCloud.

iCloud seems to remove the unopened files in documents when the hard drive is low in disk space. iCloud uploads indigo folder in documents, then deletes it.

Shows here that it was uploaded to icloud:

reverted to this, again:

So, can we move indigo config file outside of documents?

ps. I downloaded Stable Diffusion, hence I almost ran out of space 😅.

Indigo

Ha, nice find! And yes, you can move your Indigostack config files anywhere you want. I keep mine in Git so they're under version control.

nullart

I mean, can you move the config outside of document initially during initialization of the app? Don't put it in documents. Maybe install it in the user folder? Folders that are not touched by iCloud.

The auto deletion of stack is kind of destructive when the config is deleted by iCloud. IMO not a good feature for heavy development.

What do you think?

nullart

For now, I will store the file in Developers folder (not synced to iCloud) then create a symbolic link to the Documents/Indigo folder.

So far, Indigo seems to read the symbolic link.

update #1: symbolic link is not being followed. my stack is empty again.

update #2: when I clicked the + button to add a new stack, indigo created "Stack 2.indigostack" in Documents/Indigo. Why this behaviour?

nullart

This issue with icloud is really annoying. So I have to choose whether to disable iCloud or not use indigo...

Indigo

Hi, just circling back to this issue. Sorry for the delay.

I'm a little unclear on why things don't work for you if you simply move the .indigostack file out of ~/Documents/Indigo to somewhere that iCloud will leave it alone. I am not aware of any reason you'd need a symlink or anything. Indigo saves new stack files to your Documents folder but any time after that you can move that file anywhere you like and Indigo should use its new location from then on.

Besides the above, I'm curious how your Mac is configured so that it does this auto-deleting thing. I assume it happens if you have both...

System Settings > Apple ID > iCloud > Optimise Mac Storage turned on

...AND...

System Settings > General > Storage > Store in iCloud > Desktop and Documents turned on.

I can't really replicate the problem because my (free plan) iCloud is way too small to hold what's in my Desktop and Documents, and Apple in their infinite wisdom block you from using iCloud in VMs.

From a technical perspective I think the correct fix is for FSEvents to disambiguate between a file deletion and a file-deleted-by-iCloud-but-still-kinda-there situation. However I'm not turning up a lot on this front. Will keep digging.

Indigo

Gotta say, that "Optimise Mac Storage" feature is not sounding good: https://www.zdnet.com/article/optimize-mac-storage-can-make-your-files-go-poof-ask-me-how-i-know/

In thinking this through more, I'm concluding that the underlying problem is that your mac has run out of disk space. Indigo is not going to work well in a low-space environment at the best of times, as it needs to create sizeable folders inside ~/.indigo/stacks and stacks will simply fail to start up if it cannot do so.

When you combine that implicit requirement for free space with Apple's questionable implementation of "Optimise Mac Storage" I'm thinking there's no really nice way for Indigo to avoid the situation you've encountered. Asking users to choose a filesystem location for new stack config files won't help if they choose their Desktop or Documents, and I would hardly want Indigo telling them not to use those locations.

I'm hopeful that in your case freeing up some disk space will resolve the issue, perhaps combined with moving the stack config file somewhere other than your Desktop or Documents folders and/or turning off the "Optimise Mac Storage" feature altogether.