I want to add a Ticket System to the web app I'm developing.
The idea is very simple:
Users can open tickets when they have problems and
the Admin can see the tickets the users have submitted.
I'm looking for a ticket system but I have found only systems that are external to the web. I want to add it IN my wep app.
¿Do you know any ticket system por rails?
Thanks
I think using some external gem like noted above would be either an overkill or a hassle due to mentioned bad documentation.
Judging by your problem description this is quite simple to implement.
Create model for tickets and associations with users (I assume you
already have users model fully set up).
Authorize access to tickets' actions depending on user status (admin
or not)
Create corresponding views
P.S.
You could have a look at Redmine code. It is an open source project management software written in rails. I am sure this could give you a good idea of how to build your own or even borrow bits of code from there (if the app license that you are building fits)
Maybe Simple-Ticket would fit you. Though beware the basic implementation and the fact that there is no documentation provided nor written specs.
Have a look at restrospectiva. It doesn't have any documentation though
Related
I'm going to upload the app, I've been working on, on the Github and make it public. The app is a website, which is on Rails. The question is – how secure is that? Isn't making my app's code public increase the chance of breaking in?
Rails' source code is open source / public anyway, so if you're referring to someone finding a "backdoor" or something, surely it would have been done already?
--
Parts Of The Pie
The real question of uploading your code to github is whether your application is secure by doing it. This is more a question of data integrity than source code "secrets", and as #Andrew Marshall mentioned in the comments, will be more dependent on you protecting your API keys & other authentication details, than it will be about minimizing the threat of security compromise.
The other thing to remember is the modularity of Rails,
from a dependency perspective. The real value of an app is its
community - the people who care about uploading new content to it.
This means your database, partner applications, on-site experience & "marketing" are worth far more than your bare source code. Sure, the source is important, but it's just one part of the pie ;)
You'll be much better focusing on your stack (to make it extensible), your application's relevance to your community, and how you're able to extend the functionality with partner services
It all depends on how you secure your website to start. People can see all of your routes, so you need to protect restricted routes with before_action. If you have some kind of backdoor, they can see that too, so don't have one. If you follow good password encryption and login practices, you should be fine. The big file I would leave off Github is config/secrets.yml (as the name implies). But either way, most people aren't going to stumble across or care about reading your code, unless you advertise the link somewhere.
I'm looking at integrating a message board for a site I'm developing in rails. The new discourse board looks interesting http://www.discourse.org/ but there isn't much information about integrating into another site either via oauth2 or sso or perhaps using a rails engine type system. Has anyone succesfully set this up with an app like this?
thx
edit t
Is there a roadmap for how this integration could take place in the future? Parts of it look really intriguing but would like some more info on how this use case could be handled.
edit 2
Since this question is getting a fair amout of traffic, I want to add this post http://meta.discourse.org/t/integrating-discourse-with-current-user-database/6669 which goes over the SSO attempts going on at discourse currently. I have also been in contact with the people at thougtbot about their implementation.
I was interested in the same issue but here's what I found on Github issues:
The easiest way to get it running would be to install Discourse
outside of your app. We do offer the full source code if you want to
integrate with your existing login system, but I imagine it would be a
fair amount of work at this point.
Right now we haven't focused much on production deployments since
we're pre-beta and want to make sure people have a super easy upgrade
system in place to stay on top of security holes.
Not done any app with Discourse, but if their site does not provide a lot of info did you browse the Git Repository https://github.com/discourse/discourse it provides plenty of information and resources links like these ones :
Discourse Developer Install Guide (Vagrant) :
https://github.com/discourse/discourse/blob/master/docs/VAGRANT.md
Developer Advanced :
https://github.com/discourse/discourse/blob/master/docs/DEVELOPER-ADVANCED.md
Admin quick Start : https://github.com/discourse/discourse/wiki/The-Discourse-Admin-Quick-Start-Guide
Hope it can be of some help for you
Cheers
I was hoping to get some advice. I want to create an application which is like a library that holds a lot of different information including documents, pics etc where a user can log in and search for different topics and see the definition of terminology. For example users would be able to click on the word 'electical current' and a definition of electrical current would appear with also links to supporting information. The user will not be allowed to edit any information only read it.
I am wondering what is the best language to use to do this? I know that storing all the information in a html file is definitely not the way to go. But I am not sure what to use - whether html linked to a database is a good option (I've heard that this is also not great because your database code is still accessible) or whether ror is a good option. I decided that ror would be a good framework to use but I still have some doubts such as:
the application will not be hosted on the internet but only on an intranet would ror still be good for this?
the 'site' is basically static except for a few users who will have admin access although it may have more user specific functions later on.
Any advice would be great. Thanks in advance.
It seems to me that a wiki type system would be fit for your purposes. You can create one without writing any code by using a free service such as Google Sites.
I agree with #Finbarr that your problem statement sounds like it could be solved by a wiki.
I suggest mediawiki since it is open source--you can add to it or change the core software if necessary.
Or any other opensource wiki could be used. See wikipedia article
Re: which language: your problem statement is pretty broad. From what you've told us, any language would do.
Best advice: find the open source wiki that most closely meets your needs and then learn the language that it was developed in. Usually that's php or perl. But you can also find Ruby on Rails wikis such as Instiki
Added: Welcome to Stack Overflow. Note that your question is quite broad. So it may get closed for not being specific enough. Stack Overflow is aimed at answering specific questions about software programming. See the faq.
This might be a nonsensical question, but I have this task to create a rails app that shares session information, specifically login/authorization info, with an installation of a phpBB that some other person has customized to be more than just a BB.
Basically I need to rely on the user's phpBB login to authorize access to the rails app. I really don't want to have the user maintain two logins to use this conceptual single app.
I read a lot of documentation on phpBB and didn't find anything like exposed services or an API, but I'm hoping I just missed something obvious.
I've been considering adding a method to expose some hash or something to link the two applications rather than try to squeeze possibly different implementations of session.
Quick context, this work needs to be done fast and cleanly and I've never developed in php and rails is super fast so I am investigating the idea of integrating the two sides.
I might be off in the weeds, so don't be afraid to say so :)
thanks!
Have you checked phpbb-auth?
https://github.com/mattfawcett/phpbb-auth
My site requires authentication, so it has membership. I wonder if I should create my own comment system for user to discuss/comment on an article, or should just use third-party comment system like Disqus or Intense Debate, which requires seperate account (Twitter, Facebook, etc.).
In fact, it would be good if there is a guide to create my own comment system or Q&A system for users to discuss a particular article on my website. If you know of any, please lemme know.
Thanks.
I recently am working on a project where I had to weigh the same things. I eventually decided to roll my own comments.
Namely the advantage of rolling your own is that you have full control on how they work. I needed a moderation system/queue that I needed to work a specific way, for one. Second, someday I will be looking to integrate a 'community reputation' system, so that was another plus for rolling my own. Such things I don't want to leave to a third party solution outside of my control and the third parties don't always have such a flexible API to modify.
On the other hand, Disqus (or similar third party commenting systems) may be up your alley if your needs are more simple. For one, it's easy to get up and running and may be all you may really need. Accounts for it work across anything using Disqus, and that may win convenience points for your users who are sick and tired of having to sign up for a million accounts for a million websites. Disqus also has built in tools (for spam, trolls, etc) and that is also convenient.
If you go with rolling your own solution with user accounts, you can integrate things like Facebook/Twitter/etc login to make the registration process easier. But overall, like I said, depends on how fancy or complex you need the whole thing to be.
Should you roll your own, a good start is a recent Railscasts episode on the Ancestry gem http://railscasts.com/episodes/262-trees-with-ancestry, it should give you a good start on building threaded comments.
Something in the middle :) Use the acts_as_commentable plugin :
https://github.com/jinzhu/acts_as_commentable