I was looking for a simple solution to run Magento sites for local xdebug testing. I’ve figured out a lot on how to use IndigoStack so far and getting a site to load does work when setting up the DB correctly but I wanted to bring up two things:
1) For MySQL, it would be nice if there was an easier or more clear indication of needing to import an existing DB file (was stuck here for a bit, thought I had to run the database outside of IndigoStack at first). I was thinking even if it’s as simple as a text box to enter a database name to create (if it does not exist), and a button to import an existing .sql file.
2) Newer Magento versions require an additional service, Elasticsearch, in order to build/run and while I would not expect or ask for IndigoStack to have this available by default, I’m not clear on how I could install and set this up per stack as-is.
I’m sure I could install and setup Elasticsearch on my machine as it’d be accessible via localhost, but that’d lead to needing to configure it for multiple different sites outside of IndigoStack. I was curious if, since the stack is its own self contained apache server in this situation, there were some steps I could follow to get a service installed in this scope so each service is specific to each stack? Or at the least a way to add specific connection or service start commands to the specific instance (i.e. enable stack, auto spin up Elasticsearch; disable stack, spin down Elasticsearch). Is it as simple as adding a few files to the bundled apache directory (if so, how), or is there another expected process to add services to the server not available in IndigoStack?
I had an additional thought thereafter that maybe there could be a custom stack item so we could add a custom preconfigured service to run on apache/nginx. That way we can set it up once and easily apply it to any new stack we make just by tweaking a few config options available in the stack item options.