Snipe-IT upgrade

[Sheridan]

Anyone out there using Snipe-It for asset management? I've inherited a working system but it seems quite old (version 5) and I'm not sure if its updateable or I'd have to go for a new install and import the old data?

 

 

[6Foot2]

Link 1: Download Snipe-IT - Snipe-IT Free open source IT asset management [Latest version: v8.2.1  24th of July, 2025]

 

Link 2: Upgrading via Git

 

Quote

... If you installed Snipe-IT via Git (which is our recommended method - seriously, we really, really recommend it), updating Snipe-IT should be pretty straightforward. Simply pull down the newest release (using git pull) and run whatever commands the release notes specify. Your configuration won’t be overwritten, since the .env file isn't checked into version control...

 

[Sheridan]

Cheers, I think it was installed initially via git but when I try to run the update process I get an error straight away:

 

Warning: file_get_contents(https://raw.githubusercontent.com/grokability/snipe-i
t/master/.upgrade_requirements.json): Failed to open stream: No such file or dir
ectory in C:\inetpub\wwwroot\snipeit\upgrade.php on line 12

 

I can't see any documentation that suggests we can got from v5 to v8 like this - its quite a jump!

[6Foot2]

Further down the page I linked, it talks about how to upgrade manually (also how to switch go upgrade via Git)

 

😁

[Sheridan]

I've tried the manual process but it didn't seem to work. Keeping with git seems to be the best option but it fails with downloading that json file (which I can access via a browser on the same server)

 

I wonder if git/php needs to be told to use our proxy to do this

[machy]

Git can be a tetchy git with proxys

Sometimes you can just add it at cli sometimes you need to set HTTP_PROXY 

[Sheridan]

I've managed to get around the proxy with a bit of tinkering, but its let me down an absolute rabbit warren!

 

I can get the update.php to start and it generates a huge number of errors in Stage 6 (composer) and then dies at Stage 7 (putting into maintenance mode):

 

Something went wrong with downing your site. This can't be good. Please investig
ate the error. Aborting!
 

I'm starting to think that 5 to 8 is just too much of a step - we might be better off trying to start from scratch

[FragglePete]

I upgraded ours recently when I migrated it on to a new server.  I had to do incremental upgrades as going from an older version to the latest would fail - especially on database upgrades.  Wasn't the easiest of things that I've done.

 

Newer install that our current version is running I put together with Git so hoping future upgrades will be easier.

 

Pete

 

[Sheridan]

Yeah I think I might try 5-6 first and then 6-7 if that works!

 

 

[Sheridan]

11 minutes ago, FragglePete said:

I upgraded ours recently when I migrated it on to a new server.  I had to do incremental upgrades as going from an older version to the latest would fail - especially on database upgrades.  Wasn't the easiest of things that I've done.

 

Newer install that our current version is running I put together with Git so hoping future upgrades will be easier.

 

Pete

 

Did you do your incremental updates manually then?

[FragglePete]

3 hours ago, Sheridan said:

Did you do your incremental updates manually then?

 

Yes - the original install I did manually on each incremental update (about three in total I think) - when I knew the database was all up to date and backed it up.  On the new server that had the GIT installed version with the latest I then restored the database from the original server and everthing came over and all working again.

 

Pete

 

[Sheridan]

10 minutes ago, FragglePete said:

 

Yes - the original install I did manually on each incremental update (about three in total I think) - when I knew the database was all up to date and backed it up.  On the new server that had the GIT installed version with the latest I then restored the database from the original server and everthing came over and all working again.

 

Pete

 

Did you just copy over the new Snipe files and run the update.php? I'm struggling to even get 5.4 to got to 6.3 using this method! I wonder if theres just a way to export from the old, build a new empty system and import the data

[FragglePete]

Trying to remember exactly what I did - but I had to faff around with the Composer utility a fair bit to get everything in place if I remember correctly.  

 

Pete

[machy]

The Snipe Dev/s are quite friendly and helpful on there discord and may be able to offer some thoughts. 

[Sheridan]

Cheers for the info - I think I'll build a new install and see if I can export and import. Mainly because the server its currently on is a bit of a mess of old stuff and this is the only thing I want to keep!