Monday, July 06, 2009

New website

I finally took the time to redo my website properly :)

Obviously, I had to use Seaside, and as I did play with Pier some time ago, this looked like a good fit.

For those who do not know, Seaside is the best web application server I know of -- it really is something when you want to quickly write extremely complex sites or webapps. Pier is a CMS developped on top of Seaside, which provides a wiki system amongst other things.

The new theme is also frankly much better than my previous one -- it's actually nearly exactly the same as the default Pier theme, but hey, I really like it, and it _is_ cleaner :)

The site also automatically pull the last posts from this blog as well as my last commits and some recent twitter posts, and display all this as the main page.

Finally, one thing that wasn't great on the previous site was the pictures section; I resumed some earlier work I did on a Pier component (Pier Gallery) and cleaned it up to get what's shown now... more on that in a next post.


Gl0ubI said...

Great job !
Maybe you can add fancy url ;)
Or maybe it's voluntary ?

Nicolas said...

fancy url ?..

Gl0ubI said...

"Belles URL" i.e. without "seaside/pier/"

Too bad english...

Nicolas said...

ah yes :)

well, it was easier that way as I basically moved the entire old website to a new machine, with the content now served using lighttpd.

That way I can still link to all the old content exactly as before, while if I had a direct url (i.e. without seaside/pier) it would means that every request would first unnecessarily go through seaside; to overcome that I would therefore have to add specific rules in lighttpd to bypass seaside for such urls referencing static content (e.g. or the images).

I will probably do this at some point as it'd be neater (and that I don't have that many places serving old static content) but in the meantime, as I said, it meant a simpler transition... :-P

Gl0ubI said...

Yes, as i can say : "c'est pas faux :)"

Nicolas said...

Hehe :)

Sreedhar said...

I am new to GNU Step, and was curious if anyone has tips on deploying applications developed with GNUStep in a Windows 2008 Terminal Services (Remote Desktop Services) environment, as a RemoteApp.
I am having difficulty in deploying a vendor app (developed with GNUStep) on Windows 2008 RDS, as a Remote App. The app works fine when launched locally, but it is unable to locate the files, when launched as a RemoteApp (especially the ones that contain the crucial DLLs).
Any tips/thoughts would be highly appreciated.