-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Add-on configs #1842
Comments
Is |
I think we should avoid renaming the current As a counter-proposal, the |
Let's avoid making breaking changes. We can add an |
The repurposing of |
while be very important to be abel to edit/manipulate the addons config file, like core file. for debuging/troubleshooting, fixing problem, configuring some custom part that are not for the moment managed by the addon ui config part... For exemple nginx proxy manager does not provide for the moment a way to reset lost password... if the database are sqlite (the default) you need to access with sqlite3 cli to modify the database to reset the password... on haos for the moment there no simple solution available to do that... on haos the solution for the moment is to use ssh & terminal addons to dive into the nginx proxy manager container with docker exec... add sqlite package, and modify the file with sqlite cmd...
Propositions :
|
This has been implemented by #4650 🎉 |
Context
Every Add-on have a differen aproach to solve the issue if people need to be able to edit files. All the approach have the same issue, that the data are not part of the snapshot/restore/cleanup. It make also that is part feel as foreign body.
Decision
We add a new config helper they can be requested by Add-on.
/config
will be show internal inside Add-on and for the user they will have a new/config/**add-on**
folder structure for edit files./data
stay internal while/config
can be access from outside. The old/config
will be expose as/core
and need mapped withcore
flag if you want have all add-on config, the flag isdata
.For the first 2 month, we make an fallback to avoid breaking or missing folders for a soft migration.
The text was updated successfully, but these errors were encountered: