das Blog mit extra viel Sonne...

Und noch was.

by Thomas Fritzsche on 11 Sep 01:57 | 6 comments (Add Comment)
Tags: development bugs

Offenbar gibt es an vielen Stellen Bugs:

In Zusammenhang mit Omniauth habe ich diese Issues:


Ich habe Webrick gepatched:


def read_request_line(socket)
  @request_line = read_line(socket, 2024) if socket
   if @request_line.bytesize >= 2024 and @request_line[-1, 1] != LF
      raise HTTPStatus::RequestURITooLarge


Rails auf dem iMac (the usual Bugs)

by Thomas Fritzsche on 27 Aug 20:32 | 2 comments (Add Comment)
Tags: development

Inzwischen habe ich herausgefunden, dass das Problem an dem Installationsscript von oh-my-zsh liegt.
Dies hat unberechtigter Weise versucht die Ruby ENV. Variablen als permanente Einstellungen in .zshrc einzutragen und das hat natürlich alles durcheinander gewürfelt.
Inzwischen läuft es prächtig :-)

Inzwischen bin ich auf dem iMac unterwegs. Aber auch hier gibt es die eine oder andere Besonderheit die man beachten sollte.

Unter Ruby 1.9.2 kommt es manchmal zum Abbruch bei starten von Rails via rails c.

In diesem Fall hilft:

gem update --system; gem pristine --all

Dies habe ich hier gefunden:

Ein weiteres Problem tritt in Zusammenhang mit Netbeans auf. Hier kann beim Debugger der Pfad script/server nicht gefunden werden. Hier hilft:

$: << "."
before the load command in rdebug-ide (/usr/bin/rdebug-ide).
It fixed the problem. `

Den Tip habe ich hier gefunden:

Railscasts + New Blog Version

by Thomas Fritzsche on 17 Jul 23:15 | no comment (Add Comment)
Tags: development

Ryan Bates hat jede Woche etwas Neues über Ruby on Rails in seinem Screencasts Railscasts

Diese Woche geht es um Remember Me & Reset Password.
Das muste ich natürlich sofort im Blog einbauen.

Leider braucht es immer einiges an Handarbeit, da mein Blog ja I18n ist und ich somit alle Views und Controller anpassen muß. Aber es sollte (hoffentlich) jetzt funktionieren.

Blog Update

by Thomas Fritzsche on 16 Jul 19:11 | no comment (Add Comment)
Tags: development

Now with ruby based Markup and Textile processor and categories and a lot of Bugfixes.

Textile Parser / Syntax Highlighting

by Thomas Fritzsche on 27 Jun 09:41 | no comment (Add Comment)
Tags: development

I’m using a Java-Script based Textile parser and integrated a Syntaxhighlighter:

This works quite well and I can display the result while typing in the browser. Cool! However there are some disadvantages as well:

  • As there is no real html, but everything is pure Javascript and JSON, it would be difficult for search engine’s like google to scan pages based on this.
  • When I like to create Atom feeds I just have the raw-Textile source available and just can not produce html(or text) output.

Well,… I have started to create a textile parser in Ruby to be able to parse the content in the backend. While there are still several constructs missing I have already the most important constructs ready. This can be checked on Github: [link]

Meanwhile I notice that it get more and more popular to integrate Javascript within the backend (usually using Google V8 engine).
There are standalone engines (like node.js) but also integration into an Ruby stack. I still hesitate to mix up Ruby with Javascript code but if you look at Coffeescript that look promising!
Rails 3.1. is supposed to deliver some of the Javascript stuff… let’s see.

Now on GIT

by Thomas Fritzsche on 27 Jun 09:29 | 2 comments (Add Comment)
Tags: development

after working for long years using SVN I convered the repo of this Blog to GIT.
I created some test/toy repo on Github . While this is supposed to be much more effective I need to see. Meanwhile I just notice that git really is not good while performing push and pull via http (what I need in order to work with firewall proxy).
For my real repo’s I created a private git server for myself. Once the code matures I might push to GITHub as well.

What is the best time to push to public Github?

Authorization via Twitter or Google + Email confirmation

by Thomas Fritzsche on 23 Jun 10:18 | 1 comment (Add Comment)
Tags: development

I meanwhile added the fantastic Omniauth gem to my blogging application and enabled authentication via Twitter of Google.

It turns out that Twitter is easier to use than Google (via OpenID). One of my issues is that google returns different authentications depending on the requesting URL. This really sucks if your web-app is accessable by different URL’s (e.g. in development) etc. so you need to maintain another authorization for each of them.

However now it’s there and ready to use. Additionally I used the new Rails 3 mailer API to add some confirmation step for the Email Address of new Users.

SEO Friendly URLs in Rails

by Thomas Fritzsche on 23 Mar 21:27 | 1 comment (Add Comment)
Tags: development

Found some articles on how to write SEO friendly links for Rails Applications. Well…. I’m personally just like the fact that the links look cleaner:

© 2018 Thomas Fritzsche