Www

Both Pieter Colpaert and myself will hold an iRail presentation at Barcamp Antwerp tomorrow.

I’ll be discussing general things about iRail (history, future, vision), and Pieter will discuss everything related to our API.

Presentations will be put online tomorrow evening.

iRail project page is located at project.irail.be.

Also, biggest issue (station bug) seems to have been fixed in the API (mobile site soon!). Thanks Pieter Colpaert.

We’ve been busy.

First of all, big thanks for all the code and help from Pieter Colpaert.

Updates:

• API (extreme beta), thanks Pieter (wiki),
• Code clean up, improvements,
• Station bug has not been solved, yet -- working on it, (edit: fixed)
• iRail mailing list, for easy communication (wiki / archive).

And again, Git repo located here. Feel free to participate. :)

You can very easily fork my Git repository, all working improvements will be merged to the main stream.

iRail source is on Github.

To access the iRail source code;

Be aware you need to be added as contributor before being able to commit changes.

1. get Git
2. [browse to some folder] mkdir git
3. cd git
4. git clone git@github.com:Tuinslak/iRail.git
5. cd iRail
6. git fetch

To edit & commit changes:

1. git add [file]
2. git commit -m 'edited [file], added this and that'
3. git push

To update repo

1. git fetch
2. git merge origin/master

To check log

Help. Waar gaan we naartoe?!?!

Tweakers.net - PDF.

Following stations are giving a problem:

• Aalst,
• Asse,
• Brugge,
• Mechelen

Trying to find a fix.

Issue: All those stations give an additional intermediate page with the question to confirm your station choice.

Old solution: could be by-passed by adding “[B]” to the end of every station name but this has recently changed and is no longer working.

Current solution: none yet. Working with cURL to check the POST data.

Report additional broken stations to bugs@irail.be please.

After careful consideration with my lawyer Ywein Van den Brande, I have decided to put iRail back online.

The copy of the letter to the NMBS/SNCB can be viewed here.

Minor modifications have been made to make it work correctly again with the new route planner of the NMBS/SNCB (changelog); and I’ll keep working on it to optimise it (next on the todo list is a better results page). Also, feedback is always welcome… But mail me; not the NMBS/SNCB. ;)

Been slacking a bit lately, but here they are:

• /etc/nginx/nginx.conf // general nginx config
• /etc/nginx/sites-available/blog // my current (as of posting this) rproxy settings for this blog
• /etc/nginx/conf.d/proxy.conf // reverse proxy related config

Only because stats are pretty awesome. The effects of my media attention a few days ago. I’ll give some more info than what can be seen here.

And pretty happy I set up my nginx caching up a few weeks ago.

MRTG traffic stats on vm1, my nginx caching server, of the first 2 days (only major traffic source is this blog):

Top referrers (though not 100% accurate):

As I have no choice.

Geachte,

NMBS heeft onlangs vernomen dat u de uitbater bent van de website www.irail.be.

Uw website is, zoals u het zelf vermeldt, een route planner waarbij alle gegevens en informatie van NMBS website komt (“all data and info is retrieved from the B-Rail website”).

uw website maakt hergebruik van de data van NMBS. Hierdoor schendt u haar intellectuele rechten, zoals haar auteursrecht en databankrecht. Tevens maakt u zich daardoor schuldig aan het strafrechtelijk misdrijf van namaak.