Dashy update seems broken

[yuriw]

After running update for Dashy got "No Dashy Installation Found!"

Installed a fresh Dash LXC, Debian 12 default and tried update after it, got the same error.

[tteck]

#2614

[tteck]

3216604 183340b

[yuriw]

@tteck thx for quick response
I wonder when the script runs from the container, will it get the latest code?
Or you implied that I have to ‘git pull’ the latest?

[tteck]

If you had read #2614 (comment), you would have learned that the "latest" (2.1.2) breaks the installation.

Proxmox/ct/dashy.sh

Line 58 in 3216604

msg_error "There is currently no update path available."

[yuriw]

Update is still broken 😞

[tteck]

58b75e0

[yuriw]

I don’t understand what you mean if the script pull unfixed version.
Pls elaborate

[tteck]

The installation is set to only install version 2.1.1. Newer versions break the install.
There was a breaking change by changing the installation path from /dashy to /opt/dashy.
Now please explain your issue.

[yuriw]

Ok thx
I expect when I run ‘update’ script it would pull from GitHub the fixed version
I assumed it’s fixed and points to the new dir
What am I missing?

[yuriw]

yup, nothing is in /opt

root@dashy:/dashy# cd /opt/
root@dashy:/opt# ls
root@dashy:/opt#

root@dashy:/opt# cd /dashy/
root@dashy:/dashy# ls
CNAME app.json netlify.toml services
Dockerfile dist node_modules src
LICENSE docker package.json vue.config.js
Procfile docker-compose.yml public yarn.lock
README.md docs

[tteck]

Create a new Dashy LXC

[yuriw]

I understand this way. I was more interested in how to fix the old instance.
:(

[tteck]

You can try this snippet to correct the path, make sure you have a backup first just in case.

systemctl -q --now disable dashy
mv /dashy /opt/dashy
cat <<EOF >/etc/systemd/system/dashy.service
[Unit]
Description=dashy

[Service]
Type=simple
WorkingDirectory=/opt/dashy
ExecStart=/usr/bin/yarn start
[Install]
WantedBy=multi-user.target
EOF
systemctl -q --now enable dashy

Afterwards, try to update.

[yuriw]

That did work and update after as well! :)

Thx a million @tteck !

[Lissy93]

I've pushed an update (3.0.0) to Dashy which should resolve all of this.
But it does have 2 breaking changes (change in port to 8080, and change in config file location to user-data/conf.yml)

[yuriw]

I wonder if update can take those changes into account and fix them

[CrazyWolf13]

Dashy has just been updated to 3.0.1 which resolves a lot of auth related stuff.
Thank you for updating @tteck !

[yuriw]

@CrazyWolf13 worked like a charm!

[yuriw]

It is interesting now.
Dashy shows Update Available: 3.1.0 but the update says ✓ No update required. Dashy is already at 3.0.1

Any clues ?

[CrazyWolf13]

@yuriw
To be honest, that's kind of the curse and the blessing, when creating such scripts there are the people that use them, to simplify and save time, and the other part is users that don't have any idea about how it works.

While the second thing is not a problem to me, you should atleast know to never inject ANY remote script from the www UNLESS you've read through it understood it and can verify it's safe to run. There's no problem, if you need to ask ChatGPT for example, no one can know everything.

If you've read through the installation script of this dashy installer, you'd see, that the config is at the following location:
/opt/dashy/user-data/conf.yml or at /opt/dashy/public/conf.ym -> https://github.com/tteck/Proxmox/blob/main/ct/dashy.sh#L68

I can understand the frustration of you, but if you feel more comfortable with a manual installation and manually updating, then go for it, but don't expect things to run smoother.- https://dashy.to/docs/deployment here some instructions on how to deploy dashy.

And I don't agree with the term end user, YOU are the syadmin, YOU are the maintainer of that dashy instance at your home, but use the awesome helper scripts to simplify your life.

The helper scripts are awesome, they are at the best they can be, but sometimes there are changes in the applications like dashy, where tteck needs to make quick decisions on how to continue the script, to ensure it's possible to upgrade, but sometimes that process isn't always buttery smooth, so there are times where a recreation is neccessary.

If I were you, I'd go into the old broken dashy lxc, and look for the config file, at either /opt/dashy/user-data/conf.yml or
/opt/dashy/public/conf.ym then cat the file with nano, paste it into any txt file on your desktop, possibly validate the copied config file here, if there were any errors that occured while copy+pasting the conf file: https://www.yamllint.com/

Then create a new lxc, and paste in the config again.

Hope this helps you and may clear up some questions.

[yuriw]

@CrazyWolf13 I hear you and agree - the scripts are awesome!

Does it mean they can lack backward compatibility? Don't we want them to be better?

What does the error message [ERROR] in line 80: exit code 0: while executing command yarn &> /dev/null tell users?!

If update steps changed and there is no easy way to fix it, is it too much to expect to show a message and some direction on how a user can fix it instead of asking ChatGPT?

[CrazyWolf13]

@yuriw
They shouldn't lack that, but there were breaking changes due to switch from yarn to npm, but if you complain, then why not open a feature request and submit a Pull Request yourself, get active if you want something to be changed, in the open source world a lot of people invest hours of their free-time often free of charge to provide software scripts or similar. Why not support / help them a bit.

As switching from yarn to npm are big changes I guess switching over to a new lxc makes sense.

And instead of writing an ever longer text here, why not just copy out the conf.yml, backup externally create a new lxc insert the config, it will probably take less than 5 minutes.

[yuriw]

@CrazyWolf13 I must admit that the process or installing dashy via the script and restoring the settings is easy.

I still feel that giving an informational message in a situation like this, would simply users' lives and reduce questions.

Thx for your help and good discussion :)

[CrazyWolf13]

@yuriw
Glad to see, that you got it to work. :)
No problem.