Snipe-IT PHP 5.6 upgrade to 7.1
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
Instead of upgrading, why not move to a fresh box with working PHP 7.1? Keep the two separate, just copy over the database.
Because I'd have to reinstall everything. . .
Um... reinstall what? It only takes a minute. And if you scripted, or followed a script, or used Ansible, Salt, etc. it's just a push of a button away.
The scripted install uses PHP 5.6 on CentOS 7.
He would need to move to Fedora to get around that.
I just installed Snipe-IT on CentOS 7 the other day via the install.sh script and it's running PHP 7.1.13. The script kept failing on Fedora 27.
-
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
Instead of upgrading, why not move to a fresh box with working PHP 7.1? Keep the two separate, just copy over the database.
Because I'd have to reinstall everything. . .
Um... reinstall what? It only takes a minute. And if you scripted, or followed a script, or used Ansible, Salt, etc. it's just a push of a button away.
The scripted install uses PHP 5.6 on CentOS 7.
He would need to move to Fedora to get around that.
I just installed Snipe-IT on CentOS 7 the other day via the install.sh script and it's running PHP 7.1.13. The script kept failing on Fedora 27.
Damnit, I had it all workign. Did someone update
snipe.shagain? -
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
Instead of upgrading, why not move to a fresh box with working PHP 7.1? Keep the two separate, just copy over the database.
Because I'd have to reinstall everything. . .
Um... reinstall what? It only takes a minute. And if you scripted, or followed a script, or used Ansible, Salt, etc. it's just a push of a button away.
The scripted install uses PHP 5.6 on CentOS 7.
He would need to move to Fedora to get around that.
I just installed Snipe-IT on CentOS 7 the other day via the install.sh script and it's running PHP 7.1.13. The script kept failing on Fedora 27.
What happens when using the script on Fedora?
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
Instead of upgrading, why not move to a fresh box with working PHP 7.1? Keep the two separate, just copy over the database.
Because I'd have to reinstall everything. . .
Um... reinstall what? It only takes a minute. And if you scripted, or followed a script, or used Ansible, Salt, etc. it's just a push of a button away.
The scripted install uses PHP 5.6 on CentOS 7.
He would need to move to Fedora to get around that.
I just installed Snipe-IT on CentOS 7 the other day via the install.sh script and it's running PHP 7.1.13. The script kept failing on Fedora 27.
Damnit, I had it all workign. Did someone update
snipe.shagain?I had previously installed it on Fedora 26 and had no issues. I looked at some logs but honestly couldn't figure it out and didn't have the time to dedicate to troubleshooting. Just tried CentOS 7 to see if I'd get the same message and it worked flawlessly.
-
Looks like the last commit to snipe.sh was mine. it should work.
Let me poke at it.
-
Shit, there is a big pull request pending for it
-
@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@scottalanmiller said in Snipe-IT PHP 5.6 upgrade to 7.1:
Instead of upgrading, why not move to a fresh box with working PHP 7.1? Keep the two separate, just copy over the database.
Because I'd have to reinstall everything. . .
Um... reinstall what? It only takes a minute. And if you scripted, or followed a script, or used Ansible, Salt, etc. it's just a push of a button away.
The scripted install uses PHP 5.6 on CentOS 7.
He would need to move to Fedora to get around that.
I just installed Snipe-IT on CentOS 7 the other day via the install.sh script and it's running PHP 7.1.13. The script kept failing on Fedora 27.
What happens when using the script on Fedora?
I would get to the pre-flight page and everything would look good. I would have a red X next to the part about the .env file but all the settings inside it looked correct. If I clicked next, I would get a page saying that "Whoops, something went wrong". Tried to install it 4 different times with same result.
-
None of this relates to my issue of "how the H do I upgrade php without borking the whole damn thing..." lol
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
None of this relates to my issue of "how the H do I upgrade php without borking the whole damn thing..." lol
It does, because our answer is to install clean and migrate the DB.
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
None of this relates to my issue of "how the H do I upgrade php without borking the whole damn thing..." lol
It does, because our answer is to install clean and migrate the DB.
And you will get an updated version of PHP as you wish
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
None of this relates to my issue of "how the H do I upgrade php without borking the whole damn thing..." lol
It does, because our answer is to install clean and migrate the DB.
I suppose, seems painful to do that though still.
I could simply backup my .env file I suppose.
-
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
Did you attempt @black3dynamite's method above?
-
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
Did you attempt @black3dynamite's method above?
Not yet, as its mid-day and people are using the system.
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
Did you attempt @black3dynamite's method above?
Not yet, as its mid-day and people are using the system.
That would be my recommendation then. shutdown the VM, make a snapshot, then power it on and try that.
-
I just went through the git history. the installer was changed to install php 7.1 on Oct 2, 2017.
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
Did you attempt @black3dynamite's method above?
Not yet, as its mid-day and people are using the system.
That would be my recommendation then. shutdown the VM, make a snapshot, then power it on and try that.
Will do.
Would be wonderful to find a way to do this without having to "brute force it".
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?
Did you attempt @black3dynamite's method above?
Not yet, as its mid-day and people are using the system.
That would be my recommendation then. shutdown the VM, make a snapshot, then power it on and try that.
Will do.
Would be wonderful to find a way to do this without having to "brute force it".
Something in the .env file or some other config file has to point to the
php.inilocation to be used. -
@jaredbusch It's not in the .env file, looking at mine currently.
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch It's not in the .env file, looking at mine currently.
The entire point of using the IUS repo is not not use the default
php.iniwhich is PHP 5.4 on CentOS 7, so there has to be something to find thephp.inifile for the application.
