Because the .indigostack file is stored in my Documents folder, which is synced with iCloud, I customised the my.cnf file like so:

# The MySQL  Client configuration file.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

[client]
default-character-set = utf8mb4

[mysql]
prompt=indigo>
default-character-set = utf8mb4

[mysqld]
basedir="{{service_path}}"
datadir="/Users/Shared/www/mysql"
port = "{{port}}"
socket = "{{sock_file}}"
pid-file = "{{pid_file}}"
sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
max_allowed_packet = {{max_allowed_packet}}
innodb_file_per_table
lower_case_table_names = 2

# Only allow connections from localhost
bind-address = 127.0.0.1
mysqlx-bind-address = 127.0.0.1

If the stack ever shuts down, it's impossible to restart it, because it keeps wanting to reinitialise.

2022-06-07T16:04:58.364872Z 0 [System] [MY-013169] [Server] /Users/filliph/.indigo/stacks/C72FBF/mysql_A6E6/bin/mysqld (mysqld 8.0.29) initializing of server in progress as process 99625
2022-06-07T16:04:58.366415Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2022-06-07T16:04:58.366471Z 0 [ERROR] [MY-013236] [Server] The designated data directory /Users/Shared/www/mysql/ is unusable. You can remove all files that the server added to it.
2022-06-07T16:04:58.366556Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-06-07T16:04:58.366690Z 0 [System] [MY-010910] [Server] /Users/filliph/.indigo/stacks/C72FBF/mysql_A6E6/bin/mysqld: Shutdown complete (mysqld 8.0.29)  Homebrew.

I can't trust this app with my work data if I have to constantly delete the data directory in order to let MySQL reinitialise it every time I shut down Indigo or restart my computer.

Steps to reproduce:

Create a stack containing a MySQL service
Start the stack
Stop the stack
Try to start the stack again. A popup saying "Unknown" will show up, and the log file will contain the above error message about --initialize being ran on a non-empty directory.