WebSite - Backing Up

Do not forget to backup.

One of the good things about virtual machines is that, in the end, they are just a file!
Well, one ore more... But you get the idea...

To backup, just copy the files, or create a zip...

My basic idea is:
1. Create the virtual machine
2. Do the basic updates and configurations
3. Create basic backup

From this point I can create as many backups as I want, but can always reset the to the basic backup.
Can play with installation scripts until I have the right one, and then just run it against the basic instalation and have a clean system to work with.

Do not forget that backing up is not the same thing as having version control.

All the information is on the virtual machine (version control, databases, software, etc.) but you still have to have the necessary tools to work with.

But that will be on a next oportunity

WebSite - Operating System

The operating system is some what important...

There are very options, but I have decided to use Linux.
Is free and open source (some flavores).

It would take me forever to test all of then, so I decided the chose one.
My choice was UBUNTU (http://www.ubuntu.com/).

The virtual machine is VMWare Player that is also free (but not open source :-( )

The installation procedure is very simple.
Download the .iso file that has the Operation System.
I selected the desktop version. I want all the environment on one machine, so a desktop version allow me server and client tools.

Launch the VWPlayer:

Select the option create a new Virtual Machine and select the .iso file.

Configure the linux user and the name of the virtual machine as it location.

Finally decide the size of the disk file and finish the process.

Next... well, there is nothing more to do. Just install the operation System. Follow the instructions.
Simple, no?

Now we have a new virtual machine to work, without any impact on your computer.

WebSite - The enviroment

From my previous experiments, I have found that is very important to have the right tools.
You cannot do TDD with an environment that does not allow you to test the changes that you did in a very rapid way.

So I am going to start making some definitions (with no particular order):

• It has to be Open Source software
• Language: PHP
• Simple
• Every one has it (even AZURE! [http://www.windowsazure.com/en-us/develop/php/])
• Database: MySQL (yes, is still early to decide if I am going to use or not, but for now...)
• Every one has it
• Is free
• Is easy to install
• Script as much as I can 
• installations
• configurations
• Run on a virtual enviroement
• It simplifies my life
• Easy to backup
• easy to rollback (you just restore an old version of the virtual machine)
• Changes the base machine has no implication on the environment
• Create the complete environment in a single machine
• not complete sure about this one yet...

Going to create a page with the software that I am going to need and try to keep it updates [/p/configuration-files.html]

Starting a new Project - WebSite

I am going to start developing a website.
Is going to be something simple. Just a simple store with a shop car and a lite more functionality.

But I want to do it the right way!
That means using the correct Technics (what the hell does that mean?).
TDD, Continue Integration, version control, Integration tests, using Open Source projects, and so on...

It should be simple, no?