vStone Blog

A couple of days ago, I finally made up my mind about choosing sourceforge.net or google code. It became google code. It seems to me the site is a lot more responsive than the sourceforge one, and that is really all that matters for now. I don’t need complicated tools (although the webhosting sf.net provides would come in handy…).

After making a initial mistake of adding a wiki page right from the start, I could no longer reset the attached svn repository (this is only possible when you are still at r1), so I had to make a little detour by the Google-code-group. You can find the finished product here: http://code.google.com/p/kickstart-bash/. Happy issue filing!

Since the beginning of this week, I’ve been altering my code base for the Kickstart BASH script a lot. After a while, I decided it looked horrible, lacked documentation and was unmaintainable (and certainly not expandable). I also have the bad habit of forgetting what a certain function does, so proper documentation is a must.

So I started with getting back too my good old classes and objects. Starting off with the Output to HTML / Text or a File, I’m converting everything to fit nicely in classes and mainly use objects. And started documenting them all. You never know my code might prove useful to somebody else. You can expect to have a link show up to the phpdocs pretty soon.

Next up is converting my kinda ugly template system to Classes. Probably Options will prove useful here too. And I’ll be able to re-use them from my Output.

Yesterday, I finished putting up the Kickstart BASH page. More information can be found here.

At the same time, I fixed some SSL issues I was having on my home-webserver. Apparently, ssl doesn’t play nice with Namebased Virtual Hosts – which gave me some issues getting the right certificate in place. It’s a self signed one so you might get a little warning about that. It’s not going to change any time soon (as long as I’m hosting the svn repo myself that is).

Planned for later this evening: Setting up http://kickstart.vstone.org/, which will host the actual script in action. I ran into some problems again here: since my webhosting puts subdomains in a subfolder in my htdocs root, I had to do some magic rewriting to forward only ‘kickstart.vstone.org’ to the proper location.
For those of you who care: the solution was to add a rule to my wordpress rewrite rules in the .htaccess file. I’ve added the condition to check whether or not the server was accessed by ‘www.vstone.org‘ or ‘kickstart.vstone.org‘.

.htaccess file

# BEGIN WordPress
RewriteBase /
RewriteCond %{HTTP_REFERER} ^(http://|https://)(www.)?(vstone.org).*$ [NC]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{HTTP_HOST} !^kickstart.vstone.org.*$ [OR]
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress