Post by djfasching on Jan 13, 2014 20:47:57 GMT -8
Our current platform is a quad-core Dell T110 server with RAID1 drive mirroring and running Centos 6.5. The core system includes: * Apache *PHP (Latest) * Drupal 7 * Dovecot * MySQL * SendMail * SSH * VSFTPD
The server sits in a DMZ behind a PFSense firewall, connected to a Time Warner 50/5Mbs Business Cable Internet Connection.
We are currently evaluating OpenAtrium 2.12 which is built on Drupal.
I am not married to any of the current software selections, this is merely a place to start off. If it is determined that this is not up to the task at hand, I am more than willing to dump it and try something else.
Initially OpenAtrium may seem like overkill for some of what we are trying to do, but part of the appeal (aside from it being free) is that being based on the Drupal development framework makes it a very robust system to extend. On the down side, it could have scalability problems since Drupal is not the fastest CMS framework out there. You balance features, costs, and long term viability and you get what you get.
Post by brettconstable on Jan 14, 2014 3:04:48 GMT -8
I have used Atrium v1 and Drupal 6/7 for the last 3 years. They have their issues but I think all systems do. I think they are up to the initial tasks and if something better comes along lets remain open to switching being mindful of the effort to do so.
I know very little about what it takes to host these systems. I like the idea of hosted systems but if we have the skills and resources available to host ourselves then great so long as this is likely to be a medium term arrangement so that those carrying on have a system to rely on.
I agree that self-hosted may be a medium-term solution. I am self hosting at the moment partly because I had all the parts available onhand for free and because it has been my experience that when prototyping a system, it is much easier to troubleshoot when you have total and complete control.
I could see that this could evolve to having a split system model. We would host our own prototype systems for development purposes but have a hosted "Production" system. That would give us the best of all worlds.
It sounds like you are way ahead of me on the learning curve. Is there anything you would like to say about your experiences with Drupal / OpenAtrium development, functionality or ability to add / write new modules?
Post by brettconstable on Jan 15, 2014 13:56:37 GMT -8
At work we use Atrium 1 for task tracking on our help desk. I have back end access to the database from which I have created some custom queries to help track overall activity but have not done any customisation of the front end other than input to the logical organisation of all the content. I have started looking at the videos for OA2 and see the structure/terminology is quite different and with great potential for customisation but suspect our main challenge will remain with effective content organisation and management.
We are also in the process of upgrading our Drupal sites from D6 to D7. I get into some admin configuration of the sites using front end admin functions but get others to maintain modules and themes.
My experience with both is that being open source anything is possible but it is still good to get the basics working effectively before looking to far towards extensions.