Terminal Presets

joshkrz

I have a stack that contains both PHP 8.3 and 8.2.

The default preset uses 8.3 and this works great from the terminal, however I'm not sure how to create a preset that uses 8.2.

I have had a look at the docs outlined here: https://indigostack.app/docs/how-to/shell-integration/#about-terminal-presets

I have also had a look inside of the config.json of the stack bundle but no preset property exists inside of this file.

How would I create more terminal presets?

Edit: I also tried copying the default.sh file from the exports folder in the Indigo bundle, adding it to my stack bundle, renaming it and then changing the PHP version to match the one I want in my stack which didnt work.

Thanks!

Indigo

Hi @joshkrz — welcome to the forums!

You ask a great question. I also have several stacks with more than one PHP, and occasionally more than one MySQL also. As you found, the documentation states "you may create as many additional Terminal Presets as you wish." but unfortunately that is referring to an Indigo feature that is as yet unreleased.

The feature it refers to (as per screenshot above, some of which makes no sense 😜 ) is 80% complete, but after reflection I decided it was simply too complicated and 99% of users appear to have simply never needed it. Even in my own use case I would only have used it a few times. I should really remove that wording from the docs, sorry.

We have the philosophy of making 95% of things easy (usually with the GUI) and the remaining 5% of things possible (usually with overrides). So in that light, what you tried, or something very like it, should absolutely be the way to achieve this. To do so I would need to expand the override implementation a little, and also extend the current exports system to find the user-defined ones. Neither are too difficult, and I would love to implement this at some point.

In the meantime, there's a reasonably successful work-around, which is to create a second stack with the service versions you need accessible on the command line. Run it at least once so its services are all compiled. After that it should be accessible on the command line, even if the stack is not running. Indeed these presets work even if Indigo itself is not running.

Let me know how you feel about the workaround, and also if you have any thoughts on the override mechanism for when I build that out.

joshkrz

Indigo That screenshot is exactly how I imagined it to work in future! I love the preview too.

I did end up creating a new stack but of course Apache on my original stack wont use the config from the new stack and I'll also have two stack bundles.

Not a huge problem for me now now but I'll be looking at moving it into my workplace once it checks all of the boxes for us (it's almost there). Do you have a development roadmap and is there anywhere to submit feature requests?

Thanks!

Indigo

joshkrz That screenshot is exactly how I imagined it to work in future! I love the preview too

Sadly, to be clear, that screenshot describes the GUI that I ultimately decided was unneeded by most and thus shouldn't go in, replaced instead by a (future) filesystem-level override.

I'd still prefer the file override method for this; my current thinking is to have Indigo add a "starter" file into the stack bundle by default, to make customisations much easier. For example in this case it could create a file inside the bundle at /exports/custom.export.sh.SAMPLE* and that file might contain something like this:

#!/bin/sh
# Makes services from this stack accessible on the command line.
# Feel free to copy this file then uncomment and reorder the services you need.

INDIGO_PRESET_NAME="custom" # Or take this from the filename?

INDIGO_STACK_ID={{stack_id}}
INDIGO_STACK_DIR={{stack_path}}

# Apache
# source "$INDIGO_STACK_DIR/apache_9B99/export.sh"
# echo "Enabling Apache server service"

# MySQL 8.0
# source "$INDIGO_STACK_DIR/mysql_8CFA/export.sh"
# echo "Enabling MySQL server service"

# Nginx
# source "$INDIGO_STACK_DIR/nginx_819F/export.sh"
# echo "Enabling Nginx server"

# PHP 8.3
# source "$INDIGO_STACK_DIR/php_9E87/export.sh"
# echo "Enabling PHP 8.3 service"

# PHP 7.2
# source "$INDIGO_STACK_DIR/php_9E87/export.sh"
# echo "Enabling PHP 7.2 service"

# Redis
# source "$INDIGO_STACK_DIR/redis_BD3A/export.sh"
# echo "Enabling Redis service"


echo Done.

ORIGINAL_PROMPT="${ORIGINAL_PROMPT:-$PROMPT}"
PROMPT="%B%F{93}$INDIGO_STACK_ID $INDIGO_PRESET_NAME%f%b $ORIGINAL_PROMPT"

* better names gratefully accepted 🙂

Your thoughts?

To address your other two questions:

we do have an internal roadmap but nothing public at this point, mainly because of the feature freeze imposed by the release candidate phase. We're working really hard to push through that and release v1.0.0 so we can get stuck into a bunch of new features!
please feel free to submit feature requests right here in the forums! Otherwise if for any reason that doesn't feel appropriate, you're welcome to get in touch directly via email at hello@indigostack.app.