the aem extension for brackets currently only allows to configure 1 aem instance. This can cause problems when switching between projects. At startup, brackets deploys to the running AEM instance but since that may be not the instance you want to work with at the moment or the project you had open in brackets before you closed it your AEM instance gets unwanted code deployed.
It would be great if
brackets is able to handle multiple AEM configurations at a time
when brackets is started up it checks if the AEM instance it tries to connect to is the same one as it was connected before
the aem extension for brackets currently only allows to configure 1 aem instance. This can cause problems when switching between projects. At startup, brackets deploys to the running AEM instance but since that may be not the instance you want to work with at the moment or the project you had open in brackets before you closed it your AEM instance gets unwanted code deployed.
It would be great if