Maybe some of you guys are running a little Wordpress blog, like this one, too.
And maybe you also wondered, if it ist possible to integrate the sweeeet website-traffic analyzing and reporting service by google, called “Google Analytics” into your blog.

Easy !

Just download the “Ultimate Google Analytics” plugin-package from спални комплектиthe Wordpress plugins page and unzip it to th plugins directory in your wordpress installation. Let’s try it…

cd /tmp
wget http://downloads.wordpress.org/plugin/ultimate-google-analytics.zip
cd /var/www/blog.chaoz.org/wordpress/wp-content/plugins/
unzip /tmp/ultimate-google-analytics.zip

Now you just have to activate the plugin in your wordpress plugins section and you will get a new menu-item in your optins menu name “Ultimate GA”. There you have to add your google-analytics ID which looks somewhat like “UA-1234567-8″. Look it up in the javascript snippet which is shown in your google analytics account for the domain-profile in question.
I just sticked to the default options which where already set quite reasonably, I guess.

Done !

That’s right. You’re finished. Pretty easy, eh?
Now, you’ll just have to be patient and wait for the first reports to show up in your google-analytics account after some hours and visits.

cheers

~ Gerrit

cheers

~ Gerrit

If you have to type some more complex commands quite frequently, you should consider building some aliases for them.
I always load a set of basic aliases via an include in my ~/.bashrc :

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

On Ubuntu distros ~/.bash_profile will include ~/.bashrc where the real action takes place. Might be different on other distros though.

Now, here are some of the aliases I use day by day and which really save me some time. (Of course I obfuscated users and Ips a bit… )

alias ll='ls -hals --color=auto'

-> coloured dir-listings with all the details

alias l='ls -hls --color=auto'

-> same, but without hidden files

alias upgrade='sudo aptitude update && sudo aptitude dist-upgrade'

-> completely upgrade whole system to latest version; should work on ubuntu and debian based distros

alias ports='netstat -tulpen'

-> lists open/used ports without too much details

alias sp='ps faux|grep -v grep|grep -i'

-> if you provide a string as an argument to the command, it´ll grep for it in the output of ‘ps faux’

E.g.:

[12:36:37][gerrit@neuromancer:~]$ ps faux|grep -v grep|grep -i ssh
gerrit    5879  0.0  0.0   4424   544 ?        Ss   09:51   0:00          _ /usr/bin/ssh-agent /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
gerrit    5880  0.0  0.0   4424   944 ?        Ss   09:51   0:00          _ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
root      5127  0.0  0.0   5268   984 ?        Ss   09:51   0:00 /usr/sbin/sshd

versus

[12:34:28][gerrit@neuromancer:~]$ sp ssh
gerrit    5879  0.0  0.0   4424   544 ?        Ss   09:51   0:00          _ /usr/bin/ssh-agent /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
gerrit    5880  0.0  0.0   4424   944 ?        Ss   09:51   0:00          _ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
root      5127  0.0  0.0   5268   984 ?        Ss   09:51   0:00 /usr/sbin/sshd

Also nice for quick ssh-logins:

alias server1='ssh user@192.168.0.1'

-> if you´ve also implemented public-key authentication, this is going to be a one command login

alias ovpn='sudo openvpn --config /etc/openvpn/configfile.conf'

-> start openvpn-client with certain config-file

alias mntfs='sshfs user@192.168.0.1:/ /mnt/fs'

-> mount your fileserver´s home-dir to your local filesystem via sshfs

This one is nice, too:

alias bru='ssh -X user@obelix 'bru-server''

It performs a ssh login to my company´s backup-server with activated Xserver redirection and spawns the backup-program´s admin-console on the remote server. The gui output is then redirected to my local Xserver.

I hope you got the hang of it. Possibilities are endless

Unfortunately we found out (by a complaining neighbour… D´oh!), that the attic is leaking too much noise. This is of course an issue we have to fix quickly, since I don´t wanna be killed by a neighbour who has gone crazy because of constant entertainment with the finest handmade local (prog-)rock and metal

Check it out…

cheers

~ Gerrit

After having installed the latest version you just have to edit line 89 in /usr/share/envy/instun/classes.py and change

elif self.details['osname'] == 'feisty':#SUPPORT FOR FEISTY

to

elif self.details['osname'] == 'gutsy':#SUPPORT FOR FEISTY

Now you can start Envy and it should work like a charm.

cheers

~ Gerrit

If you like modern rock, metal, metalcore, emocore and the like (or whatever you like to call it), be sure to check out ChroniX Aggression

And if you also share my love for some decent drum & bass you should definitely tune in to BassDrive some time.

Have fun!

cheers

~ Gerrit

I got my shiny new Diezel VH4! Let me tell you this is THE very guitar amplifier I was always dreaming of. This monster has got four(!) completely independent channels. Which means, four completely independent pre-amp sections.

http://diezel.typo3.inpublica.de/vh4.21.0.html
http://reviews.harmony-central.com/reviews/Guitar+Amp/product/Diezel/VH4/10/1

Of course I bought it because of its great sounds and tone, but it has also got so many cool features and extras, it really is worth the fu*** money.
Built in MIDI with phantom power, one extra insert per channel, serial loop, parallel loop, mute function, etc, etc, and you can even drive this baby with different or even mixed power-tubes. Like e.g. 2xEL34 and 2×6L6 if you want to soften the raw tone of the built in TAD EL34B-STR a bit…
Now I´ve to figure out how to effectively hook up my T.C. G-Major to the loops of the VH4 and work with it properly. Probably I have to RTFM this time If anyone has some suggestions, pleeease gimme some input! I´ll add some pics of my current rig and our sweet new rehearsal room next week I guess. Be prepared

cheers

~ Gerrit

Edit: I think I´ll add an extra page where I list/document my equipment for interested gearheadz

I assume that you have a working installation of the Java-VM somewhere on your machine. The openfire startup-script searches for a JVM in some common places on your system like /usr , etc. If you have a custom installation like I have, you should put the JAVA_HOME variable in your shell-environment.

1. Download the most current package from the Ignite Realtime site.
   The version I refer to in this guide is openfire 3.3.2
2. Unzip the package to a folder where you want the installation to live in. In my case this is /opt
   

   cd /opt
   tar xzvf openfire_3_3_2.tar.gz

   This will create the subfolder “openfire”.

3. Now you should create a non priviledged user and group the service will use to run as and assign him the base-dir of the openfire installation as homedir:

   groupadd jabber
   useradd -d /opt/openfire -g jabber jabber

4. The home-dir should also be owned by the newly created user and group:

   chown -R jabber:jabber /opt/openfire

5. Create a mysql-database for openfire:

   mysql -u root -p yourmysqlrootpw

   create database jabber;
   grant all on jabber.* to jabber@localhost IDENTIFIED BY "pwfornewuser";

6. Change to the new user and start the server:

   su - jabber
   cd /opt/openfire/bin
   ./openfire start

7. Now, if you run

   netstat -tulpen

   you should see a java-process listening on ports 9090 and 9091 after a few moments.
   Server up and running.

8. To set up the basic configuration, you have to open the admin-interface in your browser:
   http://<iporhstnameofyourjabberserver>:9090
9. The basic setup is pretty staight forward. You have to choose a language setting, provide the connection-string (e.g.: jdbc:mysql://127.0.0.1:3306/jabber) and user+password for your mysql-db, a password for the admin-account of openfire and that´s it.
10. Of course you also have to make sure that the ports 5222 and 5223 (for ssl client-connections) are not firewalled since then you won´t be able to connect your client to the new server For server to server connections and file transfers you also need to open port 5269 and 7777. Server to server connections are necessary if you want to be able to communicate with people who are not logged on to your jabber-server.

If I find time, I might add some screens in the next couple of days.
If you have any questions or like to comment, feel free to do so

cheers

~ Gerrit

This is my shiny new WordPress-blog. Stay tuned to read some comments and dangerous smattering on various topics of my interest, like linux, music, guitars and equipment, recording, studying, etc. pp
And be sure not to take every word too seriously …

cheers

~ Gerrit