Skip to content
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

[BUG] StartingView = Minimal view not working #1191

Open
5 tasks done
ToniMurcia opened this issue May 22, 2023 · 12 comments
Open
5 tasks done

[BUG] StartingView = Minimal view not working #1191

ToniMurcia opened this issue May 22, 2023 · 12 comments
Assignees
Labels
👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending 🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@ToniMurcia
Copy link

Environment

Self-Hosted (Docker)

System

Docker 20.10.8

Version

2.1.1

Describe the problem

Settings like appConfig.startingView not working when you set them up on conf.yml. For example it is not posible to show the minimal view by default. If you execute yarn build, this settings start to work but then it is not possible to modify the conf.yml externally because the conf.yml that works is the one located in /app/dist/

Additional info

No response

Please tick the boxes

@ToniMurcia ToniMurcia added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label May 22, 2023
@liss-bot
Copy link
Collaborator

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

@ToniMurcia ToniMurcia changed the title [BUG] <title> [BUG] StartingView = Minimal view not working May 22, 2023
@kkoyung
Copy link

kkoyung commented Jun 10, 2023

I have the same issue. My temporary workaround is to remove /app/dist/conf.yml after executing yarn build within the container, then it will fallback to use your config file mounted at /app/public/conf.yml.

Detail procedure:

  1. Start the container with the value minimal for appConfig.startingView in your config file.
docker run -d \
  -p 4000:80 \
  -v /root/my-local-conf.yml:/app/public/conf.yml \
  --name my-dashboard \
  --restart=always \
  lissy93/dashy:latest
  1. Re-build the app within the container, by docker exec -it my-dashboard yarn build
  2. Remove the generated config file, by docker exec -it my-dashboard rm ./dist/conf.yml

Remark: You have to repeat step 2-3 whenever you make changes to the value of appConfig.startingView.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Jun 10, 2023
@liss-bot
Copy link
Collaborator

liss-bot commented Sep 9, 2023

This issue has gone 3 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

@liss-bot liss-bot added ⚰️ Stale [ISSUE] [PR] No activity for over 1 month and removed 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending labels Sep 9, 2023
@liss-bot
Copy link
Collaborator

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.

@liss-bot liss-bot removed the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Sep 14, 2023
@Lissy93 Lissy93 reopened this Dec 31, 2023
@CrazyWolf13 CrazyWolf13 added the ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed label Mar 3, 2024
@CrazyWolf13
Copy link
Collaborator

Hi
This problems seems to be related to dashy not automatically rebuilding on changes, see #1479 and #1290 (comment)
A new release has just been published, which should fix this issue, so please upgrade to the latest version.
If this is not the case just respond back to this ticket and I'll reopen this issue.
Thanks and have a nice day.

@melhakim
Copy link

melhakim commented Nov 3, 2024

Changing startingView has no effect whatsoever. I rebooted the instance, saved local, saved to disk. Looked through the filesystem. I am running it via lxc from tteck

@CrazyWolf13
Copy link
Collaborator

Please try a manual rebuild.

@melhakim
Copy link

melhakim commented Nov 3, 2024

@CrazyWolf13 do you mean from the UI? Or from the cli? I did trigger the rebuild from the UI. I still have to see how to do it from the cli.

@CrazyWolf13
Copy link
Collaborator

Yes I mean trigger from the UI, then refresh the page.

@melhakim
Copy link

melhakim commented Nov 3, 2024

Done that. No change. Tried looking for the conf.yml file in the dist dir as suggested earlier in this post and couldn't find it.

@CrazyWolf13
Copy link
Collaborator

Then it's probably a issue with dashy, I'll reopen this, but honestly wouldn't be surprised if this does not get fixed in the near future, looking at the activity and the project behind the curtains.

@CrazyWolf13 CrazyWolf13 reopened this Nov 3, 2024
@CrazyWolf13 CrazyWolf13 removed the ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed label Nov 3, 2024
@melhakim
Copy link

melhakim commented Nov 3, 2024

Thanks. I'll keep looking into it. But with my limited experience with the project as well as js, I doubt I'll get to anything faster than the collaborators.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending 🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Awaiting Triage
Development

No branches or pull requests

6 participants