For a long time now, my favorite recipe for intranet/internet content management included an ounce of ssh, a tsp of rsync and pound of shell scripting to spoon feed the user – a dish that I call ConMan.sh (Content Management). Chris happenned to leave a comment on the my previous blog post (Yo Chris!, I’ll take that Flock-Ac-Ccount plz) and I hopped over to his site only to find another interesting hop to Drupal.
In short, time to lock up that shell script and time to Drupalize the intranet. I have forums, personal webpages, static pages and pictures on my intranet that all need updating. Seems like having them under drupal will provide a good kick in every1′s pants to do so….everytime. We have a few people who know linux and a whole bunch of them who think they know linux so getting acceptance will not be a problem, i.e. if they don’t already drool on the “Hey it’s GPL” line. (Or should I shout “Hey!, its open source” to confuse them…)
I will try it. We need to re-design our intranet anyway, so might as well. Question is about attachements and that my-sql thingy. Wonder how the performance will be after it gains a few pounds…
Not only did we install drupal as our CMS system, we are migrating our entire corporate Intranet to the CMS system. In order to fully integrate the CMS with our Active Directory, I had to modify that LDAP Integration module. So much so that I am now a co-maintainer of the module.