Hi Friends
I would like to know which of these frameworks - RoR or Drupal - should be chosen for developing a new website.
The website should support the following.
- A system for - requests to be created by customers, - which get automatically assigned to engineers - request gets resolved by the assigned engineer - customer closes the request with a rating - Excellent Database support - both customers and engineers must be able to register / login to see the status of their requests. - Automatic emails on request status - Generating Reports must be easy.
- 'Social' from the ground up.
- Easy Payment Gateway Integration
- 100,000+ Hits a day
- support for Great UI. More importantly, Changes to the UI must be very easy.
A google search on the topic gives results pointing more towards Drupal (as probably the internet is dominated by PHP/Drupal developers) and am finding it hard to decide.
I also heard a suggestion to go for Microsoft ASP .NET for scalability reason- confused again :(. I do not want to "pay" for Microsoft products. I feel an open source product supported by a community of developers would be better than a Microsoft product. And that would keep the costs low as well.
Could you please give me some pointers. Once website development starts, changing the framework later on would prove to be very expensive and I want to avoid such a situation. Hence, need your expert opinions to decide now.
Please excuse if ilug is not the forum to ask such a question.
Thanks.
Shaahul Hameed
2011/5/28 Hameed shaahulhameed@gmail.com:
I would like to know which of these frameworks - RoR or Drupal - should be chosen for developing a new website.
Drupal, as far as I am aware, is a content management system. RoR's comparison should be with Django.
Binand
On 28 May 2011 22:00, Binand Sethumadhavan binand@gmail.com wrote:
Drupal, as far as I am aware, is a content management system. RoR's comparison should be with Django.
Thanks Binand.
Leaving the comparison aside, "based on my requirement" that I have posted in my last message, what should I go for - RoR, Drupal, Django or something else - and why?
Thanks a lot!
Shaahul Hameed
On Sat, May 28, 2011 at 10:10 PM, Hameed shaahulhameed@gmail.com wrote:
Leaving the comparison aside, "based on my requirement" that I have posted in my last message, what should I go for - RoR, Drupal, Django or something else - and why?
What you need isa "ticketing system" a.k.a. "Help-desk system". There are plenty of open source systems. details : http://en.wikipedia.org/wiki/Issue_tracking_system
Few open source systems:
1. http://osticket.com/ 2. List of other systems : http://www.opensourcehunter.com/2010/03/12/9-free-open-source-ticket-sytems/
-Shamit
2011/5/28 Hameed shaahulhameed@gmail.com:
Leaving the comparison aside, "based on my requirement" that I have posted in my last message, what should I go for - RoR, Drupal, Django or something else - and why?
I'd say none of the above - you should go with an existing software. I can wholeheartedly recommend RT - http://bestpractical.com/rt.
Binand
On 29 May 2011 06:38, Binand Sethumadhavan binand@gmail.com wrote: I'd say none of the above - you should go with an existing software. I can wholeheartedly recommend RT - http://bestpractical.com/rt.
On 28 May 2011 23:21, Shamit Verma subs.linux.mum@vshamit.com wrote: What you need isa "ticketing system" a.k.a. "Help-desk system". There are plenty of open source systems. details : http://en.wikipedia.org/wiki/Issue_tracking_system
Few open source systems:
- http://osticket.com/
- List of other systems :
http://www.opensourcehunter.com/2010/03/12/9-free-open-source-ticket-sytems/
Thanks a lot for suggesting Issue Tracking / Request Tracking Systems.
That's exactly what I need which would be at the core of the website. So that would be one part of the solution I am looking for.
As I mentioned in my first mail, these are my requirements:
On 28 May 2011 17:47, Hameed shaahulhameed@gmail.com wrote:
The website should support the following.
A system for
requests to be created by customers, which get automatically assigned to engineers request gets resolved by the assigned engineer customer closes the request with a rating Excellent Database support both customers and engineers must be able to register / login to see the status of their requests. Automatic emails on request status Generating Reports must be easy.
'Social' from the ground up.
Easy Payment Gateway Integration
100,000+ Hits a day
support for Great UI. More importantly, Changes to the UI must be very easy.
What I am also looking for is the "web development framework" that would best support such ticketing systems in addition to other points mentioned above - so that the website development and maintenance become easy.
I am looking for a sturdy long-term solution. Based on the frameworks / technologies you suggest, I would be off-loading the complete website development to a company with the required expertise.
Thanks.
On Sun, May 29, 2011 at 5:33 PM, Hameed shaahulhameed@gmail.com wrote:
What I am also looking for is the "web development framework" that would best support such ticketing systems in addition to other points mentioned above - so that the website development and maintenance become easy.
I am looking for a sturdy long-term solution. Based on the frameworks / technologies you suggest, I would be off-loading the complete website development to a company with the required expertise.
In that case, Drupal makes sense. Reason is, you can easily get someone to create themes etc for Drupal and it already have integration modules for "social" aspects. So, overall solution would be:
1. Use Drupal for Website. (Everything except "Issue Tracking System") 2. Add Issue Tacking features to Drupal, there are two ways: A. Use built-in Drupal module for this (http://drupal.org/project/support) B. Integrate OSTicket with Drupal
I would suggest you get cost/effort estimates for both options and decide accordingly.
-Shamit