You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user has recently posted on the forums that the version of Snipe-IT on our v18.0 appliance is a bit dated. He noted that he tried to update Snipe-IT himself but had troubles. He didn't mention what he'd tried or what went wrong, but I did a quick test myself and was able to update it relatively easily (instructions below).
It occurs to me that perhaps we could include a script to update Snipe-IT (and perhaps upstream software on other appliances?). Because we have no control over the changes between versions, there is a risk that it may potentially fail and leave the server in a broken state. And/or it might be destructive if user data already exists. So we'd need to be careful to make the risks clear.
Perhaps we could give the option to run the update script on first boot? (Noting the risk). And/or we could force (or at least encourage) users to create TKLBAM (or other) backup first?!
Another consideration is whether or not the new version will be compatible with the PHP version in the current appliance. In this case, the current latest Snipe-IT version (v7.x) works fine with the default TKL v18.0 PHP version (v8.2). However that my not be the case in the future.
I'd be interested to hear thoughts about this idea from others.
Anyway, here's the Snipe-IT update instructions:
Log into the Snipe-IT appliance terminal - as root; or on AWS MP server run sudo su first. Then run these commands:
A user has recently posted on the forums that the version of Snipe-IT on our v18.0 appliance is a bit dated. He noted that he tried to update Snipe-IT himself but had troubles. He didn't mention what he'd tried or what went wrong, but I did a quick test myself and was able to update it relatively easily (instructions below).
It occurs to me that perhaps we could include a script to update Snipe-IT (and perhaps upstream software on other appliances?). Because we have no control over the changes between versions, there is a risk that it may potentially fail and leave the server in a broken state. And/or it might be destructive if user data already exists. So we'd need to be careful to make the risks clear.
Perhaps we could give the option to run the update script on first boot? (Noting the risk). And/or we could force (or at least encourage) users to create TKLBAM (or other) backup first?!
Another consideration is whether or not the new version will be compatible with the PHP version in the current appliance. In this case, the current latest Snipe-IT version (v7.x) works fine with the default TKL v18.0 PHP version (v8.2). However that my not be the case in the future.
I'd be interested to hear thoughts about this idea from others.
Anyway, here's the Snipe-IT update instructions:
Log into the Snipe-IT appliance terminal - as root; or on AWS MP server run
sudo su
first. Then run these commands:The text was updated successfully, but these errors were encountered: