Time to Move Openfire to CentOS
-
Seems like the general install is fairly straight forward:
http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/install-guide.html -
@thanksaj said:
Couldn't you technically follow @scottalanmiller's tutorial on scottalanmiller.com for installing Elastix on CentOS and then just use the OpenFire portion? Just one thought...
I would not do that. Its an old version of OpenFire and your system is full of packages that you don't need and an old version of CentOS. Way better to install a vanilla system and just run the OpenFire RPM. No extra stuff laying around, potentially causing problems.
-
OpenFire is an easy install, not bad at all. It's all packaged up and testing on Linux already.
-
I've done a lot of OpenFire on CentOS. Very simple install.
-
@NetworkNerd What client are you using with Openfire?
-
@coliver said:
@NetworkNerd What client are you using with Openfire?
We are using Spark. Thus far it has worked pretty well for us. I know you can use other XMPP clients but have not explored them much.
-
@NetworkNerd said:
@coliver said:
@NetworkNerd What client are you using with Openfire?
We are using Spark. Thus far it has worked pretty well for us. I know you can use other XMPP clients but have not explored them much.
I've never really jumped into XMPP/jabber so I'm just feeling to waters. Spark looks like a very manageable solution though. I'm trying to figure out how chat would work in our organization since most people work out of the same office.
-
@NetworkNerd said:
@coliver said:
@NetworkNerd What client are you using with Openfire?
We are using Spark. Thus far it has worked pretty well for us. I know you can use other XMPP clients but have not explored them much.
I like Spark quite a bit but the requirement to have Java for it sucks big time. They need to make a C# or F# native .NET client for Windows and get on with it. No one uses Spark on anything but Windows, Java makes no sense.
-
@coliver said:
I've never really jumped into XMPP/jabber so I'm just feeling to waters. Spark looks like a very manageable solution though. I'm trying to figure out how chat would work in our organization since most people work out of the same office.
It's pretty awesome. XMPP is very nice and since it is free and you can control everything it is hard to go wrong. Although these days I would be tempted to just put people on HipChat, it's free and hosted by Atlassian.
NTG uses HipChat just for the developers. Change uses it too.
-
@scottalanmiller said:
@coliver said:
I've never really jumped into XMPP/jabber so I'm just feeling to waters. Spark looks like a very manageable solution though. I'm trying to figure out how chat would work in our organization since most people work out of the same office.
It's pretty awesome. XMPP is very nice and since it is free and you can control everything it is hard to go wrong. Although these days I would be tempted to just put people on HipChat, it's free and hosted by Atlassian.
NTG uses HipChat just for the developers. Change uses it too.
Is there any concern that the chats are not archived somewhere in case management needed to review? Or are they archived for that sort of thing.
-
@NetworkNerd said:
NTG uses HipChat just for the developers. Change uses it too.
Is there any concern that the chats are not archived somewhere in case management needed to review? Or are they archived for that sort of thing.
You can pay for archiving. Most companies do not want archiving. Archiving bring in legal overhead that most want to avoid.
-
@scottalanmiller said:
I've done a lot of OpenFire on CentOS. Very simple install.
Do you see any issues from using the built-in database that you can select in the OpenFire GUI?
-
You really only choose something else if you want to scale more. The built in one is pretty limited. It's the same as using SQLite, basically. MySQL is what people use when they want something more robust.
