Twilike.net - a mini-startup for commenting on movies directly from Twitter
I want to introduce a small startup with which you can rate and comment on films from Twitter, as well as view these comments. Part I. Course selection.
Studying at my university in my second year, for the first time I had to choose a course and start doing it. My choice was a small Twitter service that allows you to rate and comment on movies directly from Twitter - twilike.net .
The idea was that it’s very convenient after commenting on a movie to comment and rate it directly on Twitter (by that time, I probably already had a tweet :-)).
The next question was: what is it actually written on? Since at that time I knew only php from languages suitable for the web (but I didn’t like it very much, I don’t know why) I had to learn something new.
The choice fell on Ruby.
Part II Ruby and Sinatra.
Well, Sinatra was chosen as the web framework, I used DataMapper as the ORM. Such a choice was made thanks to articles from the Habra user-user indigo about building a home file sharing on Sinatra && DataMapper && Haml. I chose Haml as a template engine and I still remember it with great warmth :-)
I started studying ruby with the very “ drops ” of Startup Programmer and the official site of Ruby.
Ruby was studied, the first version of the site was ready here ...
Part III. Gae.
... I found out about the Google App Engine . I was inspired / impressed by the very idea of reducing the platform’s capabilities, but in return, the almost perfect vertical (or horizontal ... I don’t know :-)) application scaling! Actually, I’m still inspired by this idea :-)
I studied the “very, very, very initial” Python and wrote the simplest application for loading and scaling images, which is still used in my Tweak .
I can’t say that I worked a lot with GAE, but I liked what I saw!
Part IV VDS and the first compilation of software.
The next question that arose before me was “where is the application itself hosted?”
Unfortunately, ruby is not php and has some problems in the "hosting-for-student" niche :-) But in any case, VDS and a lot of fun were bought for two days in the form of settings for this very VDS.
It was fun, at least not to understand, why the non-working Passenger strenuously drove me into a stupor, and also took away a decent part of my spiritual balance :-)
Part V. Long live the Fragrant Rails!
At one point, looking at my “o-horror-o-trash-o-heap” MVC, I decided to ENOUGH. Sinatra is not the place here, you need to look at the big and scary Ruby On Rails .
Starting with Agile Web Development with Rails, Third Edition and making another store :-) I decided to start writing Twilike already on Rails.
Thanks Rails Guides , RailsCasts, Rails Api and Rails in general.
After the correspondence, the application became much better and turned into some “not-a-bunch-of-all” one. Also along the way, DelayedJobs and the Cells plugin were used ( thanks to RubyOnRails to russian google group ).
In general, for myself, I realized that it’s not worth writing your crutches, but you need to use and modify someone else’s :-)
Part VI. Heroku
And again, having read about Rails on Habré, Heroku hosting decided to try to use it :-) and run Twilike on it. Everything was much simpler than with my hosting - I just uploaded the application and it worked! (well, or rather almost :-))
And what surprised me the most was the fact that the application worked much faster on the free Heroku tariff plan than on my dead VDS.
Well, a little about the service itself.
It's mega simple :-) Tweet your message with the hashtag #twilike like this: “Pulp Fiction. Just looked. Best movie! # twilike + ”and after a while you watch this comment on Twilight :-)
That is, the review syntax is: Movie title. (a dot after the name is required) Comment. #twilike (+ or = or -)
Tweeter website and about section .
I would be glad if Habrausers with Twitter used Twilight :-)
Thanks to everyone who read :-)
ps I wonder how the free Heroku tariff will respond to the Habraffect :-) - of course, if there is one :-)
The next question was: what is it actually written on? Since at that time I knew only php from languages suitable for the web (but I didn’t like it very much, I don’t know why) I had to learn something new.
The choice fell on Ruby.
Part II Ruby and Sinatra.
Well, Sinatra was chosen as the web framework, I used DataMapper as the ORM. Such a choice was made thanks to articles from the Habra user-user indigo about building a home file sharing on Sinatra && DataMapper && Haml. I chose Haml as a template engine and I still remember it with great warmth :-)
I started studying ruby with the very “ drops ” of Startup Programmer and the official site of Ruby.
Ruby was studied, the first version of the site was ready here ...
Part III. Gae.
... I found out about the Google App Engine . I was inspired / impressed by the very idea of reducing the platform’s capabilities, but in return, the almost perfect vertical (or horizontal ... I don’t know :-)) application scaling! Actually, I’m still inspired by this idea :-)
I studied the “very, very, very initial” Python and wrote the simplest application for loading and scaling images, which is still used in my Tweak .
I can’t say that I worked a lot with GAE, but I liked what I saw!
Part IV VDS and the first compilation of software.
The next question that arose before me was “where is the application itself hosted?”
Unfortunately, ruby is not php and has some problems in the "hosting-for-student" niche :-) But in any case, VDS and a lot of fun were bought for two days in the form of settings for this very VDS.
It was fun, at least not to understand, why the non-working Passenger strenuously drove me into a stupor, and also took away a decent part of my spiritual balance :-)
Part V. Long live the Fragrant Rails!
At one point, looking at my “o-horror-o-trash-o-heap” MVC, I decided to ENOUGH. Sinatra is not the place here, you need to look at the big and scary Ruby On Rails .
Starting with Agile Web Development with Rails, Third Edition and making another store :-) I decided to start writing Twilike already on Rails.
Thanks Rails Guides , RailsCasts, Rails Api and Rails in general.
After the correspondence, the application became much better and turned into some “not-a-bunch-of-all” one. Also along the way, DelayedJobs and the Cells plugin were used ( thanks to RubyOnRails to russian google group ).
In general, for myself, I realized that it’s not worth writing your crutches, but you need to use and modify someone else’s :-)
Part VI. Heroku
And again, having read about Rails on Habré, Heroku hosting decided to try to use it :-) and run Twilike on it. Everything was much simpler than with my hosting - I just uploaded the application and it worked! (well, or rather almost :-))
And what surprised me the most was the fact that the application worked much faster on the free Heroku tariff plan than on my dead VDS.
Well, a little about the service itself.
It's mega simple :-) Tweet your message with the hashtag #twilike like this: “Pulp Fiction. Just looked. Best movie! # twilike + ”and after a while you watch this comment on Twilight :-)
That is, the review syntax is: Movie title. (a dot after the name is required) Comment. #twilike (+ or = or -)
Tweeter website and about section .
I would be glad if Habrausers with Twitter used Twilight :-)
Thanks to everyone who read :-)
ps I wonder how the free Heroku tariff will respond to the Habraffect :-) - of course, if there is one :-)