Dashy
-
A self-hosted startpage for your server. Easy to use visual editor, status checking, widgets, themes and tons more!
-
A self-hosted startpage for your server. Easy to use visual editor, status checking, widgets, themes and tons more!
@olearycrew it looks like a hybrid of cloudron's dashboard & uptime kuma
-
A self-hosted startpage for your server. Easy to use visual editor, status checking, widgets, themes and tons more!
@olearycrew : I've been looking at Heimdal and Flame. They both work, but I'd prefer something more, and this seems to offer more options. Would be good to see it here on Cloudron.
-
H humptydumpty referenced this topic on
-
I've managed to do a preliminary packaging of Dashy! You can find the code here.
Few notes (taken from the README):
- Dashy needs to access to edit some files on the filesystem to update the actual dashboards. It frequently updates /public/conf.yml (as well as creating backups of conf.yml files whenever a change is made), and it rewrites the entire /dist directory after a configuration change is made. This resulted in me having to put the entire /dashy directory in /app/data. Not sure if this is the right way to go about it, but it works.
- I noticed that when using the Update Configuration => Edit Config option, one must first Apply Locally or Preview Changes before writing the changes to the config file works properly. I'm going to assume that this is the behavior of the app itself, and not a result of my packaging
- When Dashy does rebuild its files after a configuration change, it ends up taking up a lot of memory. I've set mine to 1.5GB and haven't had issues. If you're seeing issues when trying to rebuild after a config change, try giving the app more resources.
-
I've managed to do a preliminary packaging of Dashy! You can find the code here.
Few notes (taken from the README):
- Dashy needs to access to edit some files on the filesystem to update the actual dashboards. It frequently updates /public/conf.yml (as well as creating backups of conf.yml files whenever a change is made), and it rewrites the entire /dist directory after a configuration change is made. This resulted in me having to put the entire /dashy directory in /app/data. Not sure if this is the right way to go about it, but it works.
- I noticed that when using the Update Configuration => Edit Config option, one must first Apply Locally or Preview Changes before writing the changes to the config file works properly. I'm going to assume that this is the behavior of the app itself, and not a result of my packaging
- When Dashy does rebuild its files after a configuration change, it ends up taking up a lot of memory. I've set mine to 1.5GB and haven't had issues. If you're seeing issues when trying to rebuild after a config change, try giving the app more resources.
@thetomester13 wonderful !!!
look forward to trying it out
-
I've managed to do a preliminary packaging of Dashy! You can find the code here.
Few notes (taken from the README):
- Dashy needs to access to edit some files on the filesystem to update the actual dashboards. It frequently updates /public/conf.yml (as well as creating backups of conf.yml files whenever a change is made), and it rewrites the entire /dist directory after a configuration change is made. This resulted in me having to put the entire /dashy directory in /app/data. Not sure if this is the right way to go about it, but it works.
- I noticed that when using the Update Configuration => Edit Config option, one must first Apply Locally or Preview Changes before writing the changes to the config file works properly. I'm going to assume that this is the behavior of the app itself, and not a result of my packaging
- When Dashy does rebuild its files after a configuration change, it ends up taking up a lot of memory. I've set mine to 1.5GB and haven't had issues. If you're seeing issues when trying to rebuild after a config change, try giving the app more resources.
@thetomester13 eventually got time to test this out
FYI I'm getting :App installation error: Installation failed: (HTTP code 500) server error - failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: mkdir /app/code/dashy: file exists: unknownJust me ? Anyone else ?
-
@thetomester13 eventually got time to test this out
FYI I'm getting :App installation error: Installation failed: (HTTP code 500) server error - failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: mkdir /app/code/dashy: file exists: unknownJust me ? Anyone else ?
@timconsidine hmm from a fresh install I'm seeing the same thing. Some quick research didn't turn up much, wondering if @girish or @nebulon have seen this error before or know where I should start looking?
-
@timconsidine hmm from a fresh install I'm seeing the same thing. Some quick research didn't turn up much, wondering if @girish or @nebulon have seen this error before or know where I should start looking?
@thetomester13 I have since "hacked" the Dockerfile and think the problem is line 25 where the WORKDIR references the no-longer-present directory (hack was to remove the
dashyfrom/app/code)I've got it past that error but it fails healthcheck as the
sedcommand instart.shfails not finding/app/data/dashy/.env(from memory, don't have the log any more). Not been able to work out the solution to that. -
@thetomester13 I have since "hacked" the Dockerfile and think the problem is line 25 where the WORKDIR references the no-longer-present directory (hack was to remove the
dashyfrom/app/code)I've got it past that error but it fails healthcheck as the
sedcommand instart.shfails not finding/app/data/dashy/.env(from memory, don't have the log any more). Not been able to work out the solution to that.@timconsidine thanks for that! I'm seeing the same thing you are. Looks like this app isn't as done as I thought it was...
I'll go back to the drawing board on this and post back when I've made some progress! -
@timconsidine hmm from a fresh install I'm seeing the same thing. Some quick research didn't turn up much, wondering if @girish or @nebulon have seen this error before or know where I should start looking?
-
@thetomester13 said in Dashy:
Some quick research didn't turn up much, wondering if @girish or @nebulon have seen this error before or know where I should start looking?
Just saw this now, do you need any help ?
@girish thanks for the offer @girish ! I think I'm alright for now. Will try and get back to this soon when I have a free few hours to play around with it. This app isn't super high on the Cloudron priority list.
The comment at https://git.cloudron.io/thetomester13/dashy-app/-/blob/master/Dockerfile#L17 says "Move /dashy to /app/data so we can write to it, and symlink it to /app/code" . Why is that so?
If you see my comment from Feb 14th (I really should get a life sometimes : ),
Dashy needs to access to edit some files on the filesystem to update the actual dashboards. It frequently updates /public/conf.yml (as well as creating backups of conf.yml files whenever a change is made), and it rewrites the entire /dist directory after a configuration change is made. This resulted in me having to put the entire /dashy directory in /app/data. Not sure if this is the right way to go about it, but it works.This is why I moved the entire folder. -
@girish thanks for the offer @girish ! I think I'm alright for now. Will try and get back to this soon when I have a free few hours to play around with it. This app isn't super high on the Cloudron priority list.
The comment at https://git.cloudron.io/thetomester13/dashy-app/-/blob/master/Dockerfile#L17 says "Move /dashy to /app/data so we can write to it, and symlink it to /app/code" . Why is that so?
If you see my comment from Feb 14th (I really should get a life sometimes : ),
Dashy needs to access to edit some files on the filesystem to update the actual dashboards. It frequently updates /public/conf.yml (as well as creating backups of conf.yml files whenever a change is made), and it rewrites the entire /dist directory after a configuration change is made. This resulted in me having to put the entire /dashy directory in /app/data. Not sure if this is the right way to go about it, but it works.This is why I moved the entire folder.@thetomester13 Ah ok. So, as a heads up, the "copy" to /app/data won't work anymore in 7.2.4 and beyond. This is because we stopped using docker volumes internally. The copying of files from a docker image's /app/data into runtime /app/data was a docker volumes feature. The fix is to do the copy in the start.sh
-
@thetomester13 Ah ok. So, as a heads up, the "copy" to /app/data won't work anymore in 7.2.4 and beyond. This is because we stopped using docker volumes internally. The copying of files from a docker image's /app/data into runtime /app/data was a docker volumes feature. The fix is to do the copy in the start.sh
-
G girish referenced this topic on
-
-
@girish ok, very good to know, thanks for the heads up!
@thetomester13 did you manage to resolve the copying issue ? does a custom install complete now ?
-
@thetomester13 did you manage to resolve the copying issue ? does a custom install complete now ?
@timconsidine I have not had a chance to look at and fix this just yet. Will be sure to update this thread when I do!
-
R robi referenced this topic on
