⚡️ Feature: Enrich configuration editor

[fahrulalwan]

Feature Description

the project configuration file only accepts compose.yaml & .env file. when i want to add new file, i had to manually create the file within ssh & adjust the user groups & permissions.

it would be nice if we have custom configuration files other than those two.

Problem It Solves

this would help with custom file configuration, other than those files. extending further capabilities in project generation.

Proposed Solution

i think this could work by adding crud feature for new files.

example: i want to setup servers.json to run pgadmin.

Alternatives Considered

No response

Additional Context

No response

Would you be willing to work on this feature?

• Yes, I'd like to implement this feature
• I could help with parts of this feature
• No, I'm just suggesting the feature

[kmendell]

Ill have to think about this one, basically your asking to be able to edit any file in the project directory?

[weedy]

This feels like unneeded feature creep. ( At least at this time )

The entire point of sexier dockge was a tool that gets a little closer to Portainer with some extra web3.0 on top.
Make the experience feel more slick in browser but your docker situation is always just flat files at your chosen mount point.

It's still all about the filesystem. You are supposed to have your file tree figured out.
My NAS does snapshots of the share and I can roll back to almost any point in time. Which is why I moved off of Portainer and the QNAP UI for docker.

When I need to put in serious work I'm using SFTP or sshfs to setup config dirs.
But for the most part containers are easy and just making a new project gets me up and running.
A quick google got me https://hub.docker.com/r/hurlenko/filebrowser if you really need a webui for file management.

[kmendell]

I do agree that this may be overkill however, i do sort of like the idea if implemented correctly, and simpliy enough but i havent put too much thought into it yet, I was more over thinking maybe like a file borwser just for the projects directory thats configured, but to your point there are containers out there so im not sure yet.

[Tealk]

Not every file needs to be included; it would be good if you could specify some files for this via the web interface. For example, config files that are used inside the container.

[cabaucom376]

I agree not everything in a project folder needs to be parsed and loaded. In addition to the "Include" directive giving you access to said files, I think you should have the ability to specify any path and have it lazily loaded to avoid too long of an initial blocking load for a project.

[xJylin]

@kmendell

This feature is actually somewhat important.
Not to be able to edit any file - But we should be atleast able to create more .env and .yaml files to edit them in the WebUI and include them in our compose.yaml

Why is this important?
Its somewhat a security concern.
You don't want everything declared in an .env file shared across all containers in the stack.
Theres good reasons to have multiple .env files in one project and assign them to each container via compose to avoid bleeding sensitive parameters into other containers.

Example use-case:
Lets say you want to have your compose files being backed up to github or anywhere else - so you cant put tokens or passwords in them directly.
You put them in an mycontainer.env and include that file in the compose.
Then you can savely upload your your yaml configs to a public space and keep the .env files private.
Otherwise you will have data either specified in the yaml directly which disables you from sharing the yaml - or you have it in the .env which is shared across all containers in the stack - which means if the container gets compromised the person is able to read all variables across the stack even if they are not relevant for that specific container.

The same is valid with global variables being basically in every container.
There should be an option to only include those that are referenced in the compose.

I do agree however that editing literally any text file does not make sense.
This is a tool to manage docker and compose after all.
Json and csv and xml and all other types are simply not part of that docker/compose-standard and are application specific.

Basically something like this would be sufficient:

And then just load whatever *.yaml / *.env file is in the project directory for editing