The good ol' boys Mike and El have created a new blog engine using Ruby + Merb + Data Mapper... it's called Feather... and if you had visited the site the last 4 hours or so, you would have noticed it was down and out... and now has a new look (well, for now)
It's pretty sweet stuff.. I imported ALL of my old items from whoisjake.com/blog and thoughtstoblog.com... using my nifty feather-mephisto plugin that you can find in feather-plugins git repo...
It's pretty cool, they got a lot of press coverage up front (read: Ruby Insider, et al)... and have put together a really light weight and unique platform. In fact, this blog is now running off of two merb processes and sqlite3 database...
At any rate, take the time to check out their project and let me know if there are any problems with the site...
Maybe, soon, I'm light as feather too :)
@Mike, @El - Thanks guys, great work on the product
@Koen - Let me know if there's any problems you come across... it should work for almost any version of Mephisto...
It’s ok now, but I encountered 2 problems:
The moment I got these out of the way, it worked like a charm! :)
Soon, I’m light as feather. ;)
Though easily hacked, this one made the most sense and covered the most grounds...
Ahh... the non-published articles, now that you say that, I don't think I actually had any in my old blog... whoops!
Glad you got those out of the way...
Hi Jake. This is the first Merb app I've looked at. I noticed they are using namespaced controllers. I started writing my own blog software with Rails and decided against namespaced controllers, because I was duplicating my view code, at least for the index/edit actions.
Is centralizing the authentication, with something like a before_filter, the primary advantage, or are there other advantages to their namespaced admin controller? Thanks.
Well the view code in this case is infinitely different on the admin side vs. the main page. Take articles for instance -- on the admin side we show a tabular view of your articles for modification. So we haven't run into a scenario where the admin side will be duplicating view code.
For a long time I was against creating a separate admin side ala Getting Real. I think it just makes a lot more sense in certain situations though. For instance where the admin side is really a lot different than articles.