Repository navigation
Requirements
Jorge Andres Arias edited this page May 15, 2025
·
1 revision
- a user should be able to create a unique bin
- each bin should be associated with two urls:
- one for sending requests to the bin
- one for viewing requests made to the bin
- when requests are made to the bin, the request method, path, headers, and body should be displayed on the UI
- a list of total requests made to a bin should be visible to the user
- the user should be able to click past requests from this list and view data for that request
- bin and request data should be stored in PostgeSQL, request payload data should be stored in MongoDB
- the application should be deployed to one team member's VPS instance
- associate a user with a specific bin, so that the same visitor can navigate back to the same bin after closing and reopening the window.
- implement real-time functionality via websockets so requests show up on the UI without a page refresh
- implement some mechanism for cleaning up requests and/or bins over time
- implement your front end using React to prepare for weeks 5-8
- create an easy way for your user to copy the endpoint or make requests
- for example, clicking a button to copy the endpoint, or a feature that let's you make custom requests from within the request bin page.
- any room to implement some AI functionality? We had a past team have their application make calls to OpenAI to write a description of the http request as a pirate 😂
- use ngrok to facilitate development
- do not expose the internals of your application by using your bin's primary key in the database as the unique URL for that bin
- save the raw request to MongoDB, even if you decide to parse values and store them in a relational way. If the request format changes and breaks your parsing logic, you don't want to lose the request entirely.