Hi, Please help me with a debate.... Who looks after your stack of software - such as in a typical LAMP environment?
I propose that in most cases, it's been the UNIX admins who put together the systems then install and basically configure the apps that make up the suite of apps that can be called an Information System such as a httpd, php/perl plus SSL/TLS and a databases such as Mysql or Postgres. Of course there are also support shared objects and so on to consider as well. They maintain all this when there is an upgrade required or if a new feature needs to be added. How are you all doing this? Do you build the system and give it away to the web developers so they can download nasty binaries that may or may not integrate well together, or do they get a system that has the httpd and so on locally compiled with site specific options? Or do you give the Oracle DBA's your Postgres or Mysql to install, grant and deploy apps in, with the web devs only doing PHP scripts and similar? Or have you got a UNIX systems programmer who designs the archictecture, build standard and methods to compile the binaries and localise them and looks after periodic code refreshes each time PHP gets another cross-site vulnerability or if mod_auth_ldap needs the mem cache option and so on? Where do you draw the line? - Who looks after the httpd.conf and who looks after the httpd and who looks after it's compilation? Who looks after your stack? Inquiring minds want to know. Discuss..... -- Rachel Polanskis Kingswood, Greater Western Sydney, Australia [EMAIL PROTECTED] http://www.zeta.org.au/~grove/grove.html "They who would give up an essential liberty for temporary security, deserve neither liberty or security" - Benjamin Franklin, 1759 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
