[Bug]: Set compose location missing

[Joly0]

Version

2026.02.11a

Unraid Version

7.2.3

Bug Description

In the previous version of this plugin (the original, not this fork) one was able to set the location of the compose file directly when creatign a new stack using "advanced options". It appears like this option is missing, therefore i cannot create new stacks with an already existing compose file somewhere on my filesystem.

This is especially useful, when a project is shipped with a pre-configured compose file that relies on the files in that directory (for example for building and stuff). Through the previous way paths to those things didnt need to be changed, as the compose file from the set location was used.
Internally this was done through the "indirect" file (filepath /boot/config/plugins/compose.manager/PROJECT/indirect) which would point to the directory of the target project containing the compose file and the .env file (if existing). This way the PROJECT folder doesnt even contain a docker-compose file or a .env file, just these files:

"Weirdly" enough, old compose stacks that used that way still work with the new plugin, i can even see the compose file and env file in the compose tab just fine. So it appears that code is still there.

Expected Behavior

Currently it seems like its not possible to set the location of a project when creating a new stack as it used to be.

Steps to Reproduce

1. Create stack with old plugin and set a path through the advanced options.
2. Create stack with new plugin and option is missing.

Relevant Logs

Compose

Additional Context

No response