Snipe-IT PHP 5.6 upgrade to 7.1
-
@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. -
@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?
-
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?
Nope. That is not how CentOS (RHEL) works.
-
@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:
@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:
@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?
Nope. That is not how CentOS (RHEL) works.
Hrm. . .
Not that I'm disagreeing, I just don't know. In following a guide on D.O. 7.1 was in pre-release at the time and not available in the repo's yet. So if I was running the process at the time I would've had to add the repo to get 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:
@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?
Nope. That is not how CentOS (RHEL) works.
Hrm. . .
Not that I'm disagreeing, I just don't know. In following a guide on D.O. 7.1 was in pre-release at the time and not available in the repo's yet. So if I was running the process at the time I would've had to add the repo to get it. . .
Those are coincidental. It was prerelease and not available in the repos. But even when released, doesn't go to the repos.
-
I guess you can try this to confirm what version is being used with apache. Add this to the /var/www/html/ or whatever your root document path is.
# phpinfo.php <?php // Show all information, defaults to INFO_ALL phpinfo(); ?> -
@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:
I assume this would be the way to remove 5.x and install 7.x
# Stop httpd and mariadb systemctl stop httpd systemctl stop mariadb # Remove all php and php modules yum -y remove php* # Add IUS Repo (Unless already added) yum -y install epel-release yum -y install https://centos7.iuscommunity.org/ius-release.rpm rpm --import /etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY # Install PHP 7.1 yum -y install php71u php71u-mysqlnd php71u-bcmath php71u-cli php71u-common php71u-embedded php71u-gd php71u-mbstring php71u-mcrypt php71u-ldap php71u-json php71u-simplexml # Start httpd and mariadb systemctl start httpd systemctl start mariadbWell this did work, which awesome thank you for that. Now using PHP 7.1.13.
Edit: I checked to see who was using the system (we have a handful and just skype'd em) and told them to give me a minute.
