While coding for quite a long time now, it is very natural for me to use Version Control systems every day. I must say that I did quite catch the hype on git and wanted to try it right away. Although I do not come from the ruby world and am more a PHP guy, I gave git a go.

Making my first repository on github an commiting some changes was really easy, no hassle and really fast response times. Whend looking at the subversion timeline it takes me almost 10-15 sec before I can see any result, when using git, even cloning is faster than that.

So I decided to use git for some small projects on my own, locally on my OS X box and shared public on github. I was fascinated by the easy branching and merging, something I always missed when using subversion, cause branching in subversion is like driving a car from the 60's.

It works, but you never know when it will break. Only one thing is for sure ... it WILL break ;).

But one thing were git loses its natural strength is when it should do what it was supposed to do, Distributed Version Control. I would have never thought that it could be so hard to maintain a git repository between two persons working on one codebase. I was working with a windows guy, and we had really some big troubles with the line endings. It took us nearly 10 commits, till the line-breaks were all set to LF.

Depending on how many persons will work on your repo, you will never fully get rid of em, and the worst of all are the 'diffs' you see in your

git log

Cause it is the whole file twice, really annoying.

But nevertheless, once you finally got it working it always produced trouble, when doing a push or a pull, cause the merges always ended in a disaster, as git's merge strategy sometimes just had overwritten some fresh changes, or just aborted and then refused to continue.

Since this did not work out, but I wouldn't wanna lose the really good merge feature, I tried git-svn. But just the first start was just a shot in the knee, here is what I did:

I cloned the SVN repo from remote, and git automatically fetched all SVN branches correctly and pulled them to local lightweight branches, so easy switching was possible.

Directly after cloning the repository, git complained, that there were some CRLF errors. Ok no worrries, just one:

git commit -a -m "Fixes the CRLF to LF"

And you're good. Then my buddy commited some stuff, and I wanted to pull the changes, so I typed:

git svn rebase First, rewinding head to replay your work on top of it...

Ahh thank you git, you recognized I had changes (the LF stuff) in my file that had not been in the remote-master

Falling back to patching base and 3-way merge... error: Your local changes to 'public/js/form/jquery.validationEngine.1.6.2.js' would be overwritten by merge. Aborting. Please, commit your changes or stash them before you can merge. Failed to merge in the changes.

Hooo, quite an error here, ok he aborted the merge, what to do now?

Actually I do not even understand why this problem occurs, cause my repo was rewinded, but anyway, lets have look on the file, cause there are supposingly some merge markers in it and I will just resolve the conflict ...

mate public/js/form/jquery.validationEngine.1.6.2.js

Hmm, no merge markers here, so I will follow git's advice

Please, commit your changes or stash them before you can merge. When you have resolved this problem run "git rebase --continue". If you would prefer to skip this patch, instead run "git rebase --skip". To restore the original branch and stop rebasing run "git rebase --abort".

So what I do is:

git commit -a -m "Added the merge" git rebase --continue

And what I get is:

No changes - did you forget to use 'git add'?

What? Ok, I give it a go

git add .

And what I get is just a newline

\n

Ok, I tried some more commands but didn't get the solution, so I recloned the repo and made:

git svn dcommit

directly after fixing the LF thing, but then other errors occured when maing my next commit. Believe this could on for ages ... I tried it back and forth, and I am 100% sure there is a solution to all of these problems, but what is the price I have to pay for this? Some git commands are so abnormal, I just can't quite remember and end up in beeing a man-page reader instead of a coder.

Working with git makes me very unproductive and gives me headaches, so I finally surrendered and switched back to SVN. Just one note here, do not even think of using git-svn, it is even worse than git alone when you are working with more than one person.

When I heard the talk of Linus Torvalds on Google, he always stated that you should use the best tool for the job. And quite frankly Torvalds, this cant seriously be the best tool for the job.

Just a simple problem, you are running a vServer and have multiple users and some of the users wants to change his password.

They type in the typical UNIX command passwd <your_passwd> or you type in as root passwd <user_name> and you get prompted for the password.

But although you got the proper permissions it just keeps saying:

passwd: Authentication information cannot be recovered
passwd: password unchanged

The german error for this is:

passwd: Authentifizierungsinformationen können nicht wiederhergestellt werden
passwd: password unchanged

Usually the problem is very easy, you just do not meet the password spcifications, but you get no detailed error on it. So just do cat /etc/pam.d/common-password

The Output should look something like this:

# # /etc/pam.d/common-password - password-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define the services to be # used to change user passwords. The default is pam_unix. # Explanation of pam_unix options: # # The "nullok" option allows users to change an empty password, else # empty passwords are treated as locked accounts. # # The "md5" option enables MD5 passwords. Without this option, the # default is Unix crypt. # # The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in # login.defs. # # You can also use the "min" option to enforce the length of the new # password. # # See the pam_unix manpage for other options. password required pam_unix.so nullok obscure md5

So you just have to fit you password to the current restrictions, in my case, the "obscure" directive caused trouble, because the password was not complicated enough. Just mix many numbers and lower/upper case letters with a minimum length in it.
"use_authtok" seems to be a troublemaker sometimes too.

Here you can find a really good step by step Tutorial who to set up MODx Revolution on multiple Domains / Sudomains.

All you need is one working Installation, cause all Domains will access the same core and will be manageable through one Backend.

This is pretty much the approach Wordpres-MU tries to accomplish, but as always, MODx does it better ;), check it out.

MODx Multi Domain Tutorial on Belafontecode.com

If you just switched to MODx Revolution and want to reactivate your favorite Snippets, here comes a good news. Ditto has already been ported and is available through thee built-in Transport Package System.

Sadly Ditto does not really work as expected if you try to work with the tutorials that have been made for the old MODx Evolution, cause some changes in Chunk-Calls and Placeholder-Calls have been introduced in Revolution.

If your experience the date to be malformed, this is due to the fact that MODx tries to reprocess the old placeholder [+date+]. Revolution has these new functionalitys called Input / Output Filters which behave very similar to PHx modifiers from MODx Evolution.

This is how my template looks when it is finished, please note that it is HTML5 compliant, if you do not want this just replace <article> with its equivalent inn HTML 4: <div>

<article class="ditto_result" pubdate="26.04.2010"> <h3 class="title"><a href="blog/tutorials/ditto-in-modx-reovlution.html" title="Ditto in MODx Reovlution">Ditto in MODx Reovlution</a></h3> <p class="byline"> by Arne Tarara on <time>26.04.2010</time></p> <div class="entry"> </div><!-- close .entry --> </article><!-- close .ditto_result -->