Installing Snipe-IT on CentOS 7 and MariaDB

jrc

Ok, so I am thinking about giving this a go for our environment. We don't track software licenses, but do track physical inventory (computers, laptops, projectors etc).

I assume I can import my current inventory into Snipe-IT via a CSV process? Can I also export to CSV?

DustinB3403

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

Ok, so I am thinking about giving this a go for our environment. We don't track software licenses, but do track physical inventory (computers, laptops, projectors etc).

I assume I can import my current inventory into Snipe-IT via a CSV process? Can I also export to CSV?

Export from what, SnipeIT?

jrc

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

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

Ok, so I am thinking about giving this a go for our environment. We don't track software licenses, but do track physical inventory (computers, laptops, projectors etc).

I assume I can import my current inventory into Snipe-IT via a CSV process? Can I also export to CSV?

Export from what, SnipeIT?

Yes, sorry. I meant export from Snipe-IT. We do this in order to comparisons and updates to some things in inventory, helps us locate devices that need to be updated and/or added.

EG - Export all Ipad 4s. Change some fields (location, assigned user etc) then re-import to update the records. This is very usefule when re-assigning iPads from classrooms onto iPad carts, or moving hundreds from one campus to another.

DustinB3403

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

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

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

Ok, so I am thinking about giving this a go for our environment. We don't track software licenses, but do track physical inventory (computers, laptops, projectors etc).

I assume I can import my current inventory into Snipe-IT via a CSV process? Can I also export to CSV?

Export from what, SnipeIT?

Yes, sorry. I meant export from Snipe-IT. We do this in order to comparisons and updates to some things in inventory, helps us locate devices that need to be updated and/or added.

EG - Export all Ipad 4s. Change some fields (location, assigned user etc) then re-import to update the records. This is very usefule when re-assigning iPads from classrooms onto iPad carts, or moving hundreds from one campus to another.

I'm not seeing an export functionality from what I have installed, but you can create reports with those details. And then subsequently upload that over your database.

DustinB3403

Speaking of iPads etc, how are you managing them. Are you using an MDM, apple configurator?

Some combination?

jrc

@dustinb3403

Jamf's Casper Suite and DEP. So MDM.

Configurator is not really a management tool, it's a setup tool to get the iPads into the MDM reasonably quickly and with minimal interaction on each device.

jrc

@dustinb3403

I'm glad to go over it with you in detail via email or PM if you like.

DustinB3403

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

@dustinb3403

I'm glad to go over it with you in detail via email or PM if you like.

Not at the moment, cause I'm tired and need a beer lol. So won't really be paying attention.

Remind me tomorrow maybe.

Emad R

@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/

scottalanmiller

@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?

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.