Here are the steps I took:

1. Install
2. Create a repo
3. Create a project
4. Import project
5. Test
6. Checkout a copy of your project

1. Install

The first step is to install Subversion on your server.

- Connect to your account with ssh and create a src directory

mkdir src
cd src

- use wget to get the subversion sources

wget http://subversion.tigris.org/downloads/subversion-deps-1.6.11.tar.gz
wget http://subversion.tigris.org/downloads/subversion-1.6.11.tar.gz

- untar the sources

tar -xzvf subversion-deps-1.4.6.tar.gz
tar -xzvf subversion-1.4.6.tar.gz

- go into the subversion folder

cd subversion-1.4.6

- install with following commands

./configure --prefix=$HOME --without-berkeley-db --with-ssl --with-editor=/usr/bin/vim --without-apxs --without-apache
make && make install

..and if a 64-bit server you need to build three main componentts and tell Apache where they are

cd apr
./configure --enable-shared --prefix=$HOME
make && make install

cd ../apr-util
./configure --enable-shared --prefix=$HOME --with-expat=builtin --with-apr=$HOME --without-berkely-db
make && make install

cd ../neon
./configure --enable-shared --prefix=$HOME --with-libs=$HOME --with-ssl
make && make install

- Configure subversion

cd ..
./configure --prefix=$HOME --without-berkeley-db --with-editor=/usr/bin/vim --with-apr=$HOME --with-apr-util=$HOME --with-neon=$HOME --withou-apxs --without-apache
make && make install

- check to see that subversion is installed

svn --version

- if installed successfully, you should see something like this:

svn, version 1.6.15 (r1038135)
   compiled Dec  6 2010, 12:13:48

Copyright (C) 2000-2009 CollabNet.

2. Create a Repo

- Create a repo

svnadmin create path/to/repo/name

- The easiest way is to cd into the directory you want to create your repo in, and then do svnadmin create reponame

3. Create a Project

- cd into your repo and create project directory

cd path/to/repo
mkdir projectname

4. Import Project

cd path/to/projectname
svn import file:///full/path/to/projectname

Checkout repo

svn checkout file:///path/to/repo

-Create files – either create new files in your repo or copy them over from somewhere else

- Add files to repo

svn add *

- Commit files

svn commit * -m "log message"

And that should be it

5. Test

Now, do a test run. Create a test folder and checkout your project

mkdir testfolder/
cd testfolder/
svn checkout file:///full/path/to/projectname

If that worked successfully, now you can move on to doing the same thing to your public_html folder, but first, make a backup of your files just to be safe

6. Checkout a Copy of Your Repo

- Delete everything in your public_html folder (or whatever folder you’re working on)

cd ../public_html
rm -rf *

- Checkout your repo

svn checkout file:///full/path/to/projectname

That’s it! Now, you can make changes in your projectname folder, commit them, and when you cd into your public_html folder you should be able to see the changes to be updated:

To see the changes:

cd public_html
svn stat -u

To update all the changes:

svn up

Because I have multiple websites on my hosted server, I will need to set up my repos a little bit differently, but following the steps above should work for you if you have one site hosted on Hostmonster.

I’m a completely new user of these tools so any tips/feedback would be great!

Official documentation can be found here.

Why Head First? Well, mostly because I’ve had a few recommendations for them. These books can be compared to The Complete Idiot’s Guides or the So You Wanna Learn [insert skill], Huh” series (the latter is how I learned HTML way back when and is what introduced me to web design).

What’s Ajax? What it’s NOT is a completely new programming knowledge. It’s a way to make your web pages more interactive and allows for asynchronous requests (requests that run in the background). Ajax uses existing technologies such as XHTML, CSS, JavaScript, the DOM, and others.

If you want to learn Ajax, I suggest that you become comfortable with XHTML, CSS, and JavaScript first. It will make learning it so much easier.

Halfway through the book I decided to stop and sharpen up my JavaScript first. Yes, I’ve seen JavaScript before but I’m not exactly an expert. And because I want to understand and become fluent in Ajax, this also needed to change. To remedy this I got myself a JavaScript book this morning.

Needless to say, I haven’t seen much sunlight this past week. But it’s all going to be worth it. I’ll have my websites “Ajaxed”  in no time! And hopefully by then I can author a post or two with live before and after samples.

Until then ..

If you’re unfamiliar with the terminology, this basically means that you can add separate “About Me,” “Blogroll,” and “100 Reasons Why I’m A Catch” pages (they currently allow up to 10 pages).

Granted, this was possible before, but you had to create a blog post and link that blog post in your layout.

The new way is much, much easier. Here’s what you do.

1. Log in at Blogger in draft (http://draft.blogger.com)
2. From the Dashboard, click the “Edit Posts” link
3. Click the “Edit Pages” link
4. Click the “New Page” button
5. Enter the Title and Body of your new page and Publish
6. Select where you would like your pages to appear
7. Save and Publish

It’s that simple!

Keep in mind that this feature is still new (which is why it is still only accessible via Blogger in Draft) and therefore likely to change AND be full of bugs. In fact, I wanted to try this out and include screen shots of the entire process and different options, but I ran into a bug. Once officially released, I’m looking forward to providing a full post on this feature.

What’s going to be on this blog? For now I intend on using this to keep readers updated on all  web design, graphic design, and art projects that I am working on (both personal and professional). In the near future, I’m hoping that I will be able to commit time to include articles that fellow web designers will find useful.

Stay tuned!

Maybe.

The issue is that there is no specific issue and therefore no specific fix.

I scoured the Web for answers and only found user solutions in various forums. For some, the problem was fixed by changing Skype settings. Others were fixed by installing Apache as a service. Others changed the port that Apache listened to by changing the configuration files.

Well, guess what? None of those things worked for me. I grew impatient trying to find my specific solution and instead opted to try out a different  WAMP until the next version of XAMPP is released (see more on Wikipedia page).