Installing Snipe-IT on CentOS 7 and MariaDB
-
I haven't used emacs since around 1990 and have never seen joe or nano. I know that people like that. I had it drilled into me in 1994 to never use anything but vi and I never have since.
-
@coliver said:
@johnhooks said:
I've definitely had times where I got stuck in some weird mode though and had no idea how to exit other than doing
:q!and losing my work.Yep... this happens with me on Debian based systems often. On CentOS I can fly through vi but on Debian systems some of the default options change and that makes working in it so much more difficult.
That's where I get it too. I still haven't figured out what they changed. Glad to see it's not just me haha.
-
@johnhooks said:
@coliver said:
@johnhooks said:
I've definitely had times where I got stuck in some weird mode though and had no idea how to exit other than doing
:q!and losing my work.Yep... this happens with me on Debian based systems often. On CentOS I can fly through vi but on Debian systems some of the default options change and that makes working in it so much more difficult.
That's where I get it too. I still haven't figured out what they changed. Glad to see it's not just me haha.
I find that avoiding Debian fixes that
-
@scottalanmiller said:
@johnhooks said:
@coliver said:
@johnhooks said:
I've definitely had times where I got stuck in some weird mode though and had no idea how to exit other than doing
:q!and losing my work.Yep... this happens with me on Debian based systems often. On CentOS I can fly through vi but on Debian systems some of the default options change and that makes working in it so much more difficult.
That's where I get it too. I still haven't figured out what they changed. Glad to see it's not just me haha.
I find that avoiding Debian fixes that
Just for the record, IRIX's vi was just as bad. Wonder if it came from the same source. Tho IRIX was an abandoned OS ~14 years ago now.
-
I've used a lot of different vi variants over the years. CentOS is actually using vim with lots of enhancements. I use very few of them, though.
-
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
-
@subi15wrx said:
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
Did you get it all working now without the error message?
-
@scottalanmiller All good Scott, thanks again to everyone for you help and patients
-
@subi15wrx said:
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
Yep, that'll do it all right. That path is one of the many things a lot of Linux Admins would take for granted.
-
@travisdh1 said:
@subi15wrx said:
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
Yep, that'll do it all right. That path is one of the many things a lot of Linux Admins would take for granted.
One of the many "things that people might assume" items I am attempting to address in that Linux Admin series.
-
I'd have another article out already if I wasn't documenting an OpenFire installation for people today.
-
@scottalanmiller said:
I'd have another article out already if I wasn't documenting an OpenFire installation for people today.
Still waiting on your ELK article
-
I feel like suddenly there are a lot of installation articles needed
-
@scottalanmiller said:
I feel like suddenly there are a lot of installation articles needed
Always were, probably more than a single person could ever cover.
-
@scottalanmiller said:
@subi15wrx said:
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
Did you get it all working now without the error message?
Hey Scott,
I just noticed today after I restarted the system I am now getting error "Error in exception handler: The stream or file "/var/www/html/snipeit/app/storage/logs/log-apache2handler-2016-02-11.txt" could not be opened: failed to open stream: Permission denied in /var/www/html/snipeit/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:87" when navigating to the home page.
shot in the dark might be permissions related?
-
@subi15wrx said:
@scottalanmiller said:
@subi15wrx said:
@travisdh1 Thanks Travis, please forgive me, my issue was I was having a hard time finding the exact path of /var/www/html/snipeit/app/config/production/app.php I am still quite a bit of a noob.
Did you get it all working now without the error message?
Hey Scott,
I just noticed today after I restarted the system I am now getting error "Error in exception handler: The stream or file "/var/www/html/snipeit/app/storage/logs/log-apache2handler-2016-02-11.txt" could not be opened: failed to open stream: Permission denied in /var/www/html/snipeit/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:87" when navigating to the home page.
shot in the dark might be permissions related?
Likely. What does this return:
ls -lh /var/www/html/snipeit/app/storage/logs/log-apache2handler-2016-02-11.txt -
This post is deleted! -
@scottalanmiller Looks like the file doesn't exist only thing in that dir is log-apache2handler-2016-02-08.txt
-
What does line 87 in here specify?
/var/www/html/snipeit/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php
-
@scottalanmiller After some digging around the internet and trial and error I was able to get it running again with the following commands
php artisan cache:clear
chmod -R 777 app/storage
php artisan dump-autoloadThen
setenforce 0
Upon reboot 'setenforce 0' has to be entered into the console again
