GithubHelp home page GithubHelp logo

options-gui's Introduction

Getting the Project to Run

To run the project turn on server first, then turn on the client. Steps Below

Turn on Server

To turn on server:

  • cd into the top level project directory. /CBOE/Backend
  • setup a virtual environment resource.
  • run: python3 -m venv venv
  • Then we must activte the virutal environment. Window run: venv\Scripts\activate.bat or ./venv/bin/activate Mac or Linux run: source myvenv/bin/activate
  • install requirements run: python -m pip install -r requirements.txt -cd into backend /CBOE/Backend/backend
  • start the server run: python manage.py runserver

Turn on Client

  • open another terminal, keep the server terminal running

  • You must have Node.js and npm installed

  • in terminal, navigate to directory: /CBOE/Frontend

  • run: npm install

  • run: npm start

The Client and Server should now be running

Note on the Implementation

  • The goal for this project was to build the closest description of the spec without making assumption
  • I used the Django Rest Framework to build the backend API
  • For this implementation I chose to omit using a database and, because of time constraint, simply used a variable to store the symbols needed for persistence. This decison was also made because there was no mention of users in the spec it is best practice not to make assumptions. I also chose not to do session server side because it is out of scope for this take home assignment.
  • Error handling on Frontend is done at all the calls to the API with .catch() menthod on axios.
  • Error handling in Backend is done when making API calls to CBOE API

What would I change if I was building this for Production

  • I would include a database and would store users and their credentials.
  • I would create a session on the backend and store the auth access_token in the Db session. Alteratively I would store an encripted acceess_token in httponly cookie and have that sent with every request to the backend in the headers.
  • I would hide the access key and secret, needed to retriev auth token, in AWS Secret Manager or something similar or even in an .env file
  • I would use a .env file
  • I would have tests both for Frontend and Backend
  • I would add some tests both for Frontend and Backend

options-gui's People

Contributors

paulalek avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.