Hi @Larke12 and welcome! And sorry it's taken me so long to respond.
Thanks for your feedback.
Re point 1: it can be hard for me to see Indigo with fresh eyes when I've spent so much time with it, but I realise the MySQL service does leave you rather on your own! Depending on a user's prior knowledge it may not be clear that you can even have a database server running and yet not have a database until you create one. Given that there are excellent apps (both free and paid) which exist solely to interact with MySQL, I'm rather inclined to simply add some "Next Steps" help text in the MySQL service, to explain what you need to do next, and to point you to use one of those apps. Would this have helped in your circumstance?
Re point 2: unfortunately no, there's no way to easily install a service of your own into the scope of an Indigo stack. To achieve this, you'd have to configure multiple Elasticsearch instances to run simultaneously, which is eminently possible, but probably difficult. (At a technical level this is because Indigo's services are independent but not isolated. They've been carefully configured to enable them to run alongside multiple other instances of the same type, but each one shares the same access rights at the OS level. In this sense there's no "stack scope" at all).
Re:
Larke12 a way to add specific connection or service start commands
and
Larke12 there could be a custom stack item
...I really like these ideas. I think both could be provided by the latter idea — essentially a "Custom Service" with user-entered start/stop commands. I personally would use this idea to start up Laravel Horizon and Vite every time I start my stack that uses those.
I've put it on my feature request list. I wish I had more hours in the day to build this stuff 🙂