sparkles
April 19th, 2009, 04:03 AM
We have a server at work serving some customers' websites that is still running 5.04. It's (un)managed by the people who maintain the websites (and they don't do that particularly well either) but because I'm the resident linux guru I'm trying to help them out with some apache problems they're experiencing at the moment.
My linux experience consists of running my own server at home, a server at work for development stuff and as a desktop at home and work, so I've never ever come close to managing public facing servers.
I'm trying to put together some basic rules for them to follow and considering my lack of experience I was hoping for some advice on how to manage the non application specific stuff like...
- only use official ubuntu repositories or mirrors
- install all security updates
- enforce password complicated-ness
- only upgrade to the LTS releases
- don't add every user to sudoers
Does that sound reasonable? Is there any other big picture stuff you could suggest? I'm particularly interested in how people decide to upgrade distro releases (if at all).
TIA
My linux experience consists of running my own server at home, a server at work for development stuff and as a desktop at home and work, so I've never ever come close to managing public facing servers.
I'm trying to put together some basic rules for them to follow and considering my lack of experience I was hoping for some advice on how to manage the non application specific stuff like...
- only use official ubuntu repositories or mirrors
- install all security updates
- enforce password complicated-ness
- only upgrade to the LTS releases
- don't add every user to sudoers
Does that sound reasonable? Is there any other big picture stuff you could suggest? I'm particularly interested in how people decide to upgrade distro releases (if at all).
TIA