https://github.com/fern4lvarez/requestapp
https://github.com/fern4lvarez/requestapp
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/fern4lvarez/requestapp
- Owner: fern4lvarez
- Created: 2012-02-10T03:40:02.000Z (about 13 years ago)
- Default Branch: master
- Last Pushed: 2012-02-14T02:04:54.000Z (about 13 years ago)
- Last Synced: 2025-01-12T10:45:38.978Z (4 months ago)
- Language: Ruby
- Homepage:
- Size: 152 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.rdoc
Awesome Lists containing this project
README
== Ruby developer challenge for Sponsorpay
This challenge consists in a web application that uses a JSON API and render render the results of the response.
It was developed with the next tools:
* Ruby 1.8.7
* Rails 3.2.1 (plus other gems)
* Ubuntu 11.10 64 bits
* Gedit + Gmate plugins
* Gnome terminal
* git
* GitHub
* Heroku
* Chrome and Firefox browsers
== Getting Started
To try this application you can download the whole repository and execute it by using the rails server that comes out-the-box or in http://requestapp.herokuapp.com/
== What's inside
We've used Ruby on Rails to create this application. There is only one controller, called Request, and two views, index and results, asociated to it. There's no models used in development.
We don't make use of any model, but we chose PostgreSQL in production environment in order not to create conflicts with Heroku, which is not SQLite3-friendly.
== Eyecandy
The views make use of a stylesheet located in the assets folder. We've used basic CSS to implement it, making some features compatible with the different availables browsers.
== How To Use It
Using RequestApp is really easy!
At the first screen you have to introduce three parameters:
* User ID (It can't be empty)
* Custom parameter (It's optional so you can let it empty)
* Page number (It must be a number)
If response is OK, results will be displayed.
If response is No Content, a message saying there's no results is displayed.
If response is Bad Request, a message will tell it.
If response was real, a green tick will appear near the logo. If it was not real, a red cross error will be there.
== Testing