We run a fairly significant Confluence installation on CentOS over VMWare, and have had no problems.
Thanks, Cary On Mon, Jul 30, 2012 at 11:13 AM, Ryan Ordway <rord...@oregonstate.edu> wrote: > I will second this. We run Confluence as well, and it worked great as long as > we didn't try to do anything fancy with it. Then we decided to expand its use > to other units on campus, which meant linking it up with an LDAP directory... > > 1. There is no facility for moving users from being local accounts to being > LDAP accounts. If you need LDAP, start with LDAP. If you need to migrate to > LDAP, you will be doing unsupported database modifications. > > 2. There is no facility for choosing which type of users you are creating. > There is no way to specify "I am creating a local account", or "I am linking > to an LDAP account". New users get created in whichever authentication source > has highest priority. To create users in other directories you have to change > their priorities, which can cause login failures if there are any naming > conflicts between authentication sources. > > 3. The authentication source priority scheme is not at all flexible. We have > run into situations where local users that had been around for years suddenly > could not login because there is a matching user in the LDAP directory, and > for various reasons we had to give the LDAP directory higher priority. > > 4. There is no facility for changing usernames. There is a feature request > for this that is many, many years old and no plans that I've heard of to > implement it. If you run into #3, then you get to learn the database schema > and develop your own code to rename users. > > 5. As a Java-based application that runs in a servlet container like Apache > Tomcat, it is very memory hungry and doesn't play well in Virtualized > environments. Atlassian recommends that Confluence NOT be run in a > virtualized environment, which can be a deal breaker for some institutions. > > For the amount of money it costs to run their software, there should be no > duct tape and chicken wire involved in its operation. > > > -- > Ryan Ordway E-mail: rord...@oregonstate.edu > Unix Systems Administrator rord...@library.oregonstate.edu > OSU Libraries, Corvallis, OR 97331 Office: Valley Library #4657 > > On Jul 25, 2012, at 6:32 AM, Sean Hannan wrote: > >> As an administrator of a Confluence installation, I have to say that I hate >> it. >> >> Confluence is fine if you are not going to be touching it or doing any kind >> of local customizations (hooking it into local auth, etc.). If that's the >> case, you should really be looking at the hosted version. >> >> I've found that Atlassian is frustrating to deal with for support. I ran >> into a bug in Confluence that has been an open ticket in their issue tracker >> for 6 years. Years. I've found upgrades to be a pain, generally, and >> sometimes Atlassian will be fast and furious with them and it's hard to keep >> up. And the longer you wait, the more painful the upgrades become. >> >> I don't deal with the money side of things, but I definitely think that we >> do not get what we pay for with Confluence. >> >> -Sean >> >> On 7/25/12 9:05 AM, "Nathan Tallman" <ntall...@gmail.com> wrote: >> >>> That's what I'm worried about with MediaWiki. The syntax used when creating >>> and editing pages isn't intuitive and I'm afraid people won't want to use >>> it. I was hoping someone would recommend a wiki with more of a WYSIWYG type >>> of editing interface. Was also hoping to stick with FLOSS, but perhaps I >>> should at least peak at Confluence. >>> >>> Thanks for the input, >>> Nathan >>> >>> On Wed, Jul 25, 2012 at 8:50 AM, Nate Vack <njv...@wisc.edu> wrote: >>> >>>> If you're expecting "everyone" to create and edit pages, >>>> it will be very hard to get widespread adoption with it. >>>> -- Cary Gordon The Cherry Hill Company http://chillco.com