cvs

Setting up a Drupal deployment, from a "where do I put the code" standpoint, is different than the setup within your actual Drupal install. It's based, quite a bit, on what you know with regards to technologies and your comfort level with them.

For example, when I first started using computers, I was Ok with using FTP. Software allowed me to connect and upload with ease. I didn't have to know the command line and frankly, knowing commands in a terminal scared me.

Flash forward a number of years and now I can't live with out it. It's just so fast. Using the command line and technologies like CVS and SVN is what allows an admin to download, update and maintain an installed codebased with much ease - but, this comes at the price of having to learn those technologies.

If you manage your own Drupal servers, and have shell access, one of your most powerful tools for deployment are CVS and SVN. Using the CVS deploy module, you can get rid of that tedious Download to computer -> upload via FTP process.

Drupal changes so fast that it's hard to keep your head above water. Only now, are many site maintainers deciding to upgrade to version 6. The biggest reason for the delay, despite the amount of time version 6 has been out, is the slow going with various modules being updated.

So the question is... "How do I keep current with modules?", and "What new modules replace the modules I've been using?".

Well, much of this lies on your shoulders - such as reading the news. Fortunately, there are some tricks you can employ to get the information you need quickly.