I am new to both Wordpress and Ruby on rails.Are these (WP and ruby on rails) two are power full tool for creating any good website .
I have seen from wordpress and ruby on rails official website that some of the popular web sites(twitter,WSJ etc.) are using these two.
Please give me are brief idea these.
It really depends on what you want, what you have and how you want it. Wordpress is 'supposed' to be a blogging CMS, but its so flexible, you can even use it for web apps. (Of course you will need to write your plugins in php). If you're looking to just have a simple website and you're not too technically inclined, I'd say Wordpress is the Go-to platform. If you have some time on your hands, seriously considering web apps, Rails is a pretty advanced web-app framework which is definitely worth a go. So really, it depends.
Well using both seems rather impractical. They both are geared toward a different use case. Rails is for web apps whereas WP is better for normal web sites.
Related
I have e-commerce site using spree. What should be ideal blog solution please suggest. Since the blog has to be updated almost daily it should be like CMS with end customer able to do the same. Should I use spree-blogging-spree gem or maybe blog hosted separately on wordpress ? What would be little scalable and convenient for a zero tech customer?
By your own definition ("zero tech customer") I would avoid any solution involving coding or custom code. Blog is an area where dozens of very good solution exists "of the shelf", so I would go for a WordPress or equivalent. You could even get the hosting done for you.
Integration can be as simple as putting the blog on a subdomain, for example if your ecommerce is hosted at pikachu-go.com, you could have blog.pikachu-go.com to point to the WordPress instance.
This means that the blog & ecommerce are totally independant, which should be for the best. You'll have a bit of work to ensure visual consistency between both, but a good palette and a logo may be enough to start.
If for any reason you really need the blog to be part of the same codebase (against, I advice against that), you may want to have a look to blogs that can be added to your Rails application as Engine such as https://buttercms.com/rails-blog-engine/ or https://github.com/kiddsoftware/rails_blog_engine.
Per the doc:
Engines can be considered miniature applications that provide
functionality to their host applications
So this is a way to deploy it inside your Spree app without resorting to custom code.
Me and a bunch of our friends decided to make a website with ruby on rails. Our question is whether refinerycms is fit with out website. What we are building is a place where our community would sign in and post up a bunch of pictures, videos, live streams, or articles/blogs. The front page would be have top feeds and featured articles. That is the idea for the most part. We thought about refinerycms but after looking into refinery it doesn't seem so fit and was wondering if its better if we just start it from scratch.
If you don't know rails and don't want to spend many hours learning.(I love it. It's fun, but not for everyone), go for wordpress.
Wordpress is easier to set up and deploy to a server.
All web hotels usually works with PHP and Mysql out of the box, witch wordpress depends on
Rails depends on ruby and that makes the server configuration more complex.
For a developer Ruby on rails is gold. But, if your main focus is to get a blog up, its to much to learn.
If you want to learn ROR go to railscast and get a pro subscription. It's the best way to pick up rails tricks
If your website mostly functions as a blog, the Refinery would be a great choice, IMHO. On the other hand, expect to do some programming on your own part if you need features such as the ones you mentioned (i.e. Live streams). On the other hand, if you're completely new to Rails, the it might be slightly more challenging, but don't let that stop you. :)
Some ruby gems like jekyll, toto and webby offer out of the box blog-type integration into your ruby app. Another way of developing a rich web blog-type application is to build and model the application yourself using pure ruby and rails practices. (e.g creating an Article and User model). The first offers out of the box features the 2nd option offers more customization and control.
In people's experience on Stack Overflow, which would be the best route and what would people consider when making the decision to use a gem out of the box versus going alone?
All of the gems you mentioned take static, markdown/textile/etc files and turn them into HTML websites. They take different approaches to it, with jekyll spitting out the finished website for hosting, toto doing the converting and routing on request, and webby doing the same as jekyll mostly.
If you're using Rails, it's important to note that none of these will integrate into your application well. They're built to more-or-less operate on their own.
Generally speaking, if a gem has the functionality you need, use it. They are not equivalent to plugins you find for Wordpress and Drupal where they are typically low-quality, buggy, poorly documented, etc. More often than not, gems simply add a couple modules that you can integrate into your application how you like.
On the other hand, a basic blog is pretty quick and simple in Rails, especially considering you've got a handy walkthrough guide straight from the Rails documentation on how to do it.
If you're new to Rails and want tight integration with your app, it's probably best to bake your own blog features.
This will take some time to do, but its worth it to learn how things really work.
If you're more seasoned, just look at the gem's API and documentation and decide if it does what you want it to do and if you're comfortable with how to integrate it. If so, it'll save you time.
One other consideration: who will be using the blog? Is it for internal use, and programmers will be the ones updating it? If that's the case, then you can make it very easy by not worrying about a lot of aesthetic polish in the back-end. Conversely, if you're making an app that includes a blogging component for the general public you might want it to feel more polished. In this case a gem might save you a lot of time.
It depends on your application.
I've been learning the Ruby web framework Sinatra lately, and I'm finding it great to use. Most of the articles and blogs I have read about it seem to assume that it is good only for small websites, or 'tiny' web-apps. Is this true? Can a complete web application be built in Sinatra, or is Ruby on Rails the way to go?
You could, in theory, build an entire web application using Sinatra, and it would offer you more precision control than Ruby on Rails would.
That said, it also removes all of the nice features ruby on rails gives you, such as the Model-View-Controller architecture.
If you're looking to build a web application with database interaction, I strongly advise you use Ruby on Rails.
If you're looking to build a very simple API or something that just takes some data and throws it up onto Twitter or something, go ahead and use Sinatra.
There is no reason that it couldn't be used to build an enterprise website. It's fast and intuitive. Two key things in building a larger web application. While it does lack many of the features of Rails, I am yet to run into a road block.
I personally like the slim nature of Sinatra. It embraces routing instead of making it a headache.
I usually find myself wrestling with Rails, whereas I configure Sinatra to my liking.
As for database interaction, mongo_mapper + Sinatra works very well.
between ruby on rails and codeigniter, which framework is better (and why) for a website with
user management
profile pages
subscriptions
blog
upload/download
Both of the frameworks you mention could handle a web site with those requirements.
You should also add Django and Symfony to your list of possible choices as they too would suit your needs.
Do you have any experience in building applications with Ruby/PHP/Python?
That depends on which language you favour. Pretty much any web framework could do all of those things. I'd personally favour Codeigniter, as PHP is more widely supported on hosting platforms.
Technically, I also think both platforms are equally capable of doing the things you want. In such cases, other things become important, such as the size of the community and hosting options. In that case, PHP and CI would be a clear winner over RoR.