code-institute-submissions / issue-tracker-6 Goto Github PK

Welcome to Problem Solver, a community-driven site where you can report bugs or request features. If user want immediate responses from admin user have to pay for that. These money help us improve our site.

These website help user to fix there problem in coding and user can request there feature to help improve the website.These project is presented simply so user can easily understand what they can do.

• In Initial commit I accidentally added my secret key, in real world projects I am sure I am not going to added that If I did I will change my secret key.
• If user didn't reply even though that solution worked the status of issue will never changed by admin.
• After cancel the comment delete-confirmation,user will take to edit comment it because they maybe accidentally clicked the delete button because edit button is next to delete button.
• Advantages of making payment for high priority in issues is user can edit issues and they will get immediate response from admin and also they can see how many views they got for there issue.

Overall my target audience are amature in coding and freshers to these coding life. Wireframe

• website have user login and user register
• user can add issues using add issue form
• user can search the issues
• other user can also help users to solve their issues by comment form

• already planned to add dislike and like button using ajax and django but not yet implemented

In this section, I mention main languages, frameworks, libraries, and any other tools that I used to construct this project.

• Bootstrap:
  • I used a Bootstrap for Responsiveness and Grid
• Django:
  • The whole project mainly depend on Django.
• Materialize css:
  • I used materializecss for icons and nav-mobile view.
• AWS:
  • I used AWS to host my static and image files.
• Stripe
  • Used stripe for payment because stripe will do secure stuffs we don't have to worry
• Chart js
  • Used chart js to show working proccess by chart

For testing I used Travis and django testcase. In django testcase I tested every single app and few other views and forms. for examples,

tested_add_issue_form Reason for these test is to check the add issue form cannot be created only with title I mean the user have to fill the every single field. Result: these test is passed.

tested_search_view_and_index_page reason for tested these to check the url is occured and to see that both views are using right templates. result:These test are passed

Another way I tested the website acted like user to check the functionality is working

I used Chrome development tool to testing my website responsible in smaller screen and in large screen.

• The website is quite responsive and works best on both large middle and small screen.
• The look and feel remains the same in different sizes

This project was deployed on Heroku

• git remote add heroku
• create procfile
• web: gunicorn tracker.wsgi:application in procfile
• used Gunicorn WSGI web application
• Push to Heroku --> $ git push heroku master

• Procfile will help to declares types -> web Website

Code Institute Mentor Chris Zielinski