Closed chevdor closed 1 month ago
Hi
This has been discussed before: https://github.com/Lissy93/dashy/issues/1570
Dashy's config loading is fully dynamic, however smaller things like adding files (icons), changing default view, auth.... still require a rebuild, and as lissy was a bit busy, we tried without the rebuild on the container reboot, however this lead to quite some issues and we hotfix/reverted this back to the yarn build-and-start
command.
I will close this issue as a duplicate.
Environment
Self-Hosted (Docker)
System
K8S
Version
3.1.1
Describe the problem
Dashy builds in
/app/dist
and unlikeuser-data
that is customizable via ENV,/app/dist
seems to be hardcoded (please tell me if this is not the case).I was thrilled to read:
and it looks like it is not very close to be true for most scenarii... but not yet for all :)
Dashy itself does not need much resources, and since my K8S limits are low, I alos run into a:
which should be read as "it is ok, it just takes longer than expected".
Since the build takes a while, to avoid a new build, I considered mounting a volume for
/app/dist
. This however fails when using a NFS share since, during the build, dashy attempts tormdir /app/dist
and the root of a NFS share cannot be removed.I understand that wiping the dist folder is easier when an upgrade is required. I hope it triggers only on upgrades btw :)
This NFS issue is not typical to dashy (people often run into it when using NFS shares, k8s and databases for instance). The Solution is known and simple: let the user define the
/app/dist
location with an ENV. This would allow telling dashy to work in say/app/dist/subdist
(subdist
is an example, it could befoobar
, the key point is that it is a folder under the/app/dist
mounting point).The NFS share is then still mounted as
/app/dist
but using a sub folder, allows to let the build script to control thesubdist
folder (and remove it). It is not possible and won't be possible for the build script (or anything else for that matter) to rm/chmod/chown the root of the NFS share, in this example/app/dist
.Additional info
No response
Please tick the boxes