You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: this is more of an RFC as I intend to implement this myself and submit a PR.
The problem
Adding multiple fields/variables is tedious. Workarounds do exist, but they are not elegant. While a solution like supporting full docker-compose syntax for templates would be arguably better, I think just having the ability to toggle a "list mode" for adding such things would already suffice and would be backwards-compatible with current templates.
The proposal
Add a checkbox (or special field type) to enable multi-line input for variables/labels/volumes/devices.
Alternatively, these could be fixed fields hidden behind the advanced mode. That's probably easier to implement.
Processing these and adding to the final docker run command should be easy enough.
Complications
The fields would probably be significantly different from the existing ones in that it must contain the definition of both keys and values (for variables/labels) or container mount and host path (for volumes/devices). This is not an issue if the decided implementation is based around fixed fields hidden behind the advanced mode.
In both cases, supporting the same syntax used by docker-compose is likely a good idea. There is no support for env files, naturally, but at least the same separators can be used, making copy-pasting from such files easier.
The text was updated successfully, but these errors were encountered:
I don't know if it's the same thing as you thought, but I like OpenWRT's luci-app-dockerman option:
It has an option called Resolve CLI
You click on it, paste the docker create or docker run command, and then submit it to the backend, the backend parses the command, and the page/form reloads with all fields filled
step1:
step2:
step3
All fields was filled and you are able to customize mode before creating the container
Strictly speaking, that's actually a next step I was going to propose once I had done these. Essentially I'd like it to support maybe also the Docker compose syntax for defining services.
(And I'd rather work on the logic by hand than trusting an LLM to hallucinate the right code. Parsing a command is easy enough so that porting from the logic in Lua is likely not the best path forwards here anyway. Very likely I'll have to rewrite whatever it produces anyway.)
Disclaimer: this is more of an RFC as I intend to implement this myself and submit a PR.
The problem
Adding multiple fields/variables is tedious. Workarounds do exist, but they are not elegant. While a solution like supporting full docker-compose syntax for templates would be arguably better, I think just having the ability to toggle a "list mode" for adding such things would already suffice and would be backwards-compatible with current templates.
The proposal
Add a checkbox (or special field type) to enable multi-line input for variables/labels/volumes/devices.
Alternatively, these could be fixed fields hidden behind the advanced mode. That's probably easier to implement.
Processing these and adding to the final docker run command should be easy enough.
Complications
The fields would probably be significantly different from the existing ones in that it must contain the definition of both keys and values (for variables/labels) or container mount and host path (for volumes/devices). This is not an issue if the decided implementation is based around fixed fields hidden behind the advanced mode.
In both cases, supporting the same syntax used by docker-compose is likely a good idea. There is no support for env files, naturally, but at least the same separators can be used, making copy-pasting from such files easier.
The text was updated successfully, but these errors were encountered: