Installing Snipe-IT on CentOS 7 and MariaDB

Emad R

@scottalanmiller said in Installing Snipe-IT on CentOS 7 and MariaDB:

@emad-r said in Installing Snipe-IT on CentOS 7 and MariaDB:

@scottalanmiller

Hi,

this guide no longer works on latest Centos

CentOS Linux release 7.3.1611 (Core)

I am starting to think that those install helper scripts from dev do more damage than good, and manual way are longer but better:

https://www.tecmint.com/install-snipe-it-asset-management-on-centos-ubuntu-debian/

Which part is broken now?

the script will actually report to you that it is finished installing successfully and you can browse to to your site, and it never works. so no real error was displayed. I reran everything a couple of times, same result.

I dont want you to test or re-write anything, its their installer script and they changed it. Either that or I screwed something up but I sticked to the defaults.

If you ask me installer scripts are nice and all, but they distance you from understanding the whole process, the guide I listed is not very accurate, for instance he actually use this command:
systemctl enable start httpd
but it will make you understand the whole process and troubleshoot it better.

DustinB3403

@emad-r try setenforce 0 and the go to the IP address.

JaredBusch

@emad-r said in Installing Snipe-IT on CentOS 7 and MariaDB:

@scottalanmiller said in Installing Snipe-IT on CentOS 7 and MariaDB:

@emad-r said in Installing Snipe-IT on CentOS 7 and MariaDB:

@scottalanmiller

Hi,

this guide no longer works on latest Centos

CentOS Linux release 7.3.1611 (Core)

I am starting to think that those install helper scripts from dev do more damage than good, and manual way are longer but better:

https://www.tecmint.com/install-snipe-it-asset-management-on-centos-ubuntu-debian/

Which part is broken now?

the script will actually report to you that it is finished installing successfully and you can browse to to your site, and it never works. so no real error was displayed. I reran everything a couple of times, same result.

I dont want you to test or re-write anything, its their installer script and they changed it. Either that or I screwed something up but I sticked to the defaults.

If you ask me installer scripts are nice and all, but they distance you from understanding the whole process, the guide I listed is not very accurate, for instance he actually use this command:
systemctl enable start httpd
but it will make you understand the whole process and troubleshoot it better.

You are not supposed to know how to install this from scratch. The developers supported method is to run the install.sh.

If you do it any other way, then you need to accept that if it fails, it is your problem.

This worked on 7.3 a couple months ago when I submitted the pull request to change it to use git on CentOS 7.

I can test again later this week.

hobbit666

Anyone done an Upgrade to V4 yet???? Got any notes/guides to do it smoothly

black3dynamite

@hobbit666 said in Installing Snipe-IT on CentOS 7 and MariaDB:

Anyone done an Upgrade to V4 yet???? Got any notes/guides to do it smoothly

I haven't upgraded yet. But I did my initial install using option 1(git clone).
There is a detail documentation for upgrading.
https://snipe-it.readme.io/v4.0/docs/upgrading-to-v4

DustinB3403

@hobbit666 said in Installing Snipe-IT on CentOS 7 and MariaDB:

Anyone done an Upgrade to V4 yet???? Got any notes/guides to do it smoothly

I upgraded yesterday and it was a bit of a bitch to get done.

DustinB3403

This is roughly what I had to do (with the help of @tiagom and Hinsk from Gitter)

cd /var/www/html/snipeit/
git pull
nano composer.json

Edit : "doctrine/inflector": "1.2.*" to be "doctrine/inflector": "1.1.*"

save the file

remove these files rm bootstrap/cache/config.php rm bootstrap/cache/services.php and rm bootstrap/cache/compiled.php

composer dump

php artisan cache:clear
php artisan view:clear
php artisan config:clear

git pull

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload

nano .env
adding
APP_LOCALE=en and LEGACY_APP_KEY=<duplicate_APP_KEY_value

php artisan migrate

Reboot and the site should work.

DustinB3403

Of course - create a backup first!

It took us a few times in getting this process sorted out as there is an issue from the master branch and develop branch.

hobbit666

@dustinb3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:

This is roughly what I had to do (with the help of @tiagom and Hinsk from Gitter)

cd /var/www/html/snipeit/
git pull
nano composer.json

Edit : "doctrine/inflector": "1.2.*" to be "doctrine/inflector": "1.1.*"

save the file

remove these files rm bootstrap/cache/config.php rm bootstrap/cache/services.php and rm bootstrap/cache/compiled.php

composer dump

php artisan cache:clear
php artisan view:clear
php artisan config:clear

git pull

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload

nano .env
adding
APP_LOCALE=en and LEGACY_APP_KEY=<duplicate_APP_KEY_value

php artisan migrate

Reboot and the site should work.

Having issues upgrading.
One issue I have is can't remember the original install method but I think I used the install.sh method from 1st post.

so I've cd into /var/www/html/snipeit

git pull that seems to bring new files down
vi composer.json looked at the file and doctrine/inflector": "1.2." is already set to 1.1.

rm bootstrap/cache/config.php says there is no file ???

composer dump gives me composer: command not found

Could I backup the DB do a fresh install the restore? or has the structure changed in the DB???

DustinB3403

@hobbit666 said in Installing Snipe-IT on CentOS 7 and MariaDB:

@dustinb3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:

This is roughly what I had to do (with the help of @tiagom and Hinsk from Gitter)

cd /var/www/html/snipeit/
git pull
nano composer.json

Edit : "doctrine/inflector": "1.2.*" to be "doctrine/inflector": "1.1.*"

save the file

remove these files rm bootstrap/cache/config.php rm bootstrap/cache/services.php and rm bootstrap/cache/compiled.php

composer dump

php artisan cache:clear
php artisan view:clear
php artisan config:clear

git pull

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload

nano .env
adding
APP_LOCALE=en and LEGACY_APP_KEY=<duplicate_APP_KEY_value

php artisan migrate

Reboot and the site should work.

Having issues upgrading.
One issue I have is can't remember the original install method but I think I used the install.sh method from 1st post.

so I've cd into /var/www/html/snipeit

git pull that seems to bring new files down
vi composer.json looked at the file and doctrine/inflector": "1.2." is already set to 1.1.

rm bootstrap/cache/config.php says there is no file ???

composer dump gives me composer: command not found

Could I backup the DB do a fresh install the restore? or has the structure changed in the DB???

This is the upgrade process (as it should work). But I believe I had the same issue. You might want to jump onto gitter and ask them to assist you with that as I don't recall what I had to do to correct it.

hobbit666

@dustinb3403 Yeah that's the procedure I've been trying to follow then tried what you mentioned above.

OK i'll have a look gitter and see what I can work out But will leave it till Monday now

black3dynamite

Have anyone installed Snipe-IT by using option 1 and then upgraded successfully to v4?

Alex Sage

@scottalanmiller said in Installing Snipe-IT on CentOS 7 and MariaDB:

vi app/config/app.php

This is wrong

Should be:

vi config/app.php

It's no longer in the app directory.

Alex Sage

Looks like timezone is set to UTC by default now.

Alex Sage

@scottalanmiller said in Installing Snipe-IT on CentOS 7 and MariaDB:

php artisan app:install

This also no longer works as of version 3...

Alex Sage

Also, nothing about opening firewall ports in this guide.

black3dynamite

This post is deleted!

hobbit666

Alex Sage

@hobbit666 Did you reboot?

Is httpd running? MariaDB?

hobbit666

@aaronstuder maybe

Will give it another go tomorrow maybe