Installing osTicket 1.10 on CentOS 7
-
@ntozier said in Installing osTicket 1.10 on CentOS 7:
@scottalanmiller as a side note, one of the most reported issues with osTicket under CentOS is that SELinux has some rules that conflict with some of the AJAX requests. If you get a white bar or find that something doesn't work you would want to check your logs to see if that's whats happening.
Thanks for the tip. I've not seen anything with CentOS 7 yet.
-
@ntozier said in Installing osTicket 1.10 on CentOS 7:
@gjacobse
Of users? Yes.
Go to Agent panel -> Users -> Click Import.He's actually being super obtuse and actually wanted to ask if you specifically had an importer script for Spiceworks tickets. It's a very specific and very complex task, I'm afraid.
-
@scottalanmiller said in Installing osTicket 1.10 on CentOS 7:
He's actually being super obtuse and actually wanted to ask if you specifically had an importer script for Spiceworks tickets. It's a very specific and very complex task, I'm afraid.
The folks over on the paid side (Customization Services) might have the ability to do something like that. But I certainly do not have a script like that, and it is definitely not baked into the product. I'm sure that it is something that they could work with people to do though.
-
@scottalanmiller said in Installing osTicket 1.10 on CentOS 7:
@ntozier said in Installing osTicket 1.10 on CentOS 7:
@scottalanmiller as a side note, one of the most reported issues with osTicket under CentOS is that SELinux has some rules that conflict with some of the AJAX requests. If you get a white bar or find that something doesn't work you would want to check your logs to see if that's whats happening.
Thanks for the tip. I've not seen anything with CentOS 7 yet.
I ran into it following your guys to get this installed... I had to
chcon -t httpd_sys_rw_content_t /var/www/html/helpdesk -RTo get it to make it past the setup where it was checking to see if the config file was writeable.
-
@ntozier said in Installing osTicket 1.10 on CentOS 7:
@gjacobse
Of users? Yes.
Go to Agent panel -> Users -> Click Import.I should have been more specific - I do see that you can import Users - But what about tickets from another system?
We have about a thousand tickets and history which would be nice to have online and searchable.
-
@gjacobse said in Installing osTicket 1.10 on CentOS 7:
@ntozier said in Installing osTicket 1.10 on CentOS 7:
@gjacobse
Of users? Yes.
Go to Agent panel -> Users -> Click Import.I should have been more specific - I do see that you can import Users - But what about tickets from another system?
We have about a thousand tickets and history which would be nice to have online and searchable.
"Another system" is, again, not at all useful. Each "system" is totally unique. If that other system saved in osTicket's format, importing would be trivial. But the assumption is that it does not. So the format that it uses is what matters. This is not a question that can be asked generically.
-
It can be done, but it is not trivial. I've done similar conversions from another system to SW.
-
@dafyre said in Installing osTicket 1.10 on CentOS 7:
It can be done, but it is not trivial. I've done similar conversions from another system to SW.
Definitely can be done. Custom script is going to be required.
-
@scottalanmiller Or you could just keep the old system around for archival and research.
-
@scottalanmiller said in Installing osTicket 1.10 on CentOS 7:
@dafyre said in Installing osTicket 1.10 on CentOS 7:
It can be done, but it is not trivial. I've done similar conversions from another system to SW.
Definitely can be done. Custom script is going to be required.
Would the same script be usable by anyone converting from SpiceWorks to osTicket?
-
@Dashrender said in Installing osTicket 1.10 on CentOS 7:
@scottalanmiller said in Installing osTicket 1.10 on CentOS 7:
@dafyre said in Installing osTicket 1.10 on CentOS 7:
It can be done, but it is not trivial. I've done similar conversions from another system to SW.
Definitely can be done. Custom script is going to be required.
Would the same script be usable by anyone converting from SpiceWorks to osTicket?
It depends on who writes the script. Because some folks in Spiceworks use Custom Fields to death, lol. That would make it that much harder to accurately transfer the data over.
If somebody can share their Spiceworks DB, I could come up with something... Just make an admin account and pass me the backup copy.
-
@Dashrender said in Installing osTicket 1.10 on CentOS 7:
@scottalanmiller said in Installing osTicket 1.10 on CentOS 7:
@dafyre said in Installing osTicket 1.10 on CentOS 7:
It can be done, but it is not trivial. I've done similar conversions from another system to SW.
Definitely can be done. Custom script is going to be required.
Would the same script be usable by anyone converting from SpiceWorks to osTicket?
It would be generic, of course. All osTicket and SW databases are the same as each other respectively.
-
Got my eval VM running. Thanks for the guide @scottalanmiller and @dafyre for the extra command to get it going
Quick question if this VM is only going to run osTickets why not just place it in the www root instead of a subfolder like helpdesk or tickets etc.
-
@hobbit666 said in Installing osTicket 1.10 on CentOS 7:
Got my eval VM running. Thanks for the guide @scottalanmiller and @dafyre for the extra command to get it going
Quick question if this VM is only going to run osTickets why not just place it in the www root instead of a subfolder like helpdesk or tickets etc.
Because it's proper convention to give each website it's own folder. Using WWW is poor practice.
-
@hobbit666 said in Installing osTicket 1.10 on CentOS 7:
Got my eval VM running. Thanks for the guide @scottalanmiller and @dafyre for the extra command to get it going
Quick question if this VM is only going to run osTickets why not just place it in the www root instead of a subfolder like helpdesk or tickets etc.
You can if you want, but that's messy. Why not just point your web server to the right place
-
@DustinB3403 said in Installing osTicket 1.10 on CentOS 7:
Because it's proper convention to give each website it's own folder. Using WWW is poor practice.
But if the only "website" is osTickets
-
@hobbit666 said in Installing osTicket 1.10 on CentOS 7:
@DustinB3403 said in Installing osTicket 1.10 on CentOS 7:
Because it's proper convention to give each website it's own folder. Using WWW is poor practice.
But if the only "website" is osTickets...
.... it's still good practice.
Where do you put the new version when you go to update, where do you store your A/B flip backups? There are real reasons that people who do this never put things in the root, no matter what use case.
It's like saying "should I virtualize when I have only one workload?" Of course, that there were two or more was never the reason that we did that in the first place.
-
@dafyre Thanks a lot! I just stuck at that point as well!
-
Just installed this tonight and have been testing it out. So far, seems pretty basic, but functional. Does anyone know how this compares to FreshDesk?
-
@fuznutz04 said in Installing osTicket 1.10 on CentOS 7:
Just installed this tonight and have been testing it out. So far, seems pretty basic, but functional. Does anyone know how this compares to FreshDesk?
Do not, I'm afraid. Have not used FreshDesk. osTicket is a little basic, but a lot of the functionality just requires taking the time to customize it for your needs, too. So far, we are still liking it.
