Empty input when searching for stocks should cause an error message to appear.

• Record here: https://github.com/hgzimmerman/SWEN344-web-project/blob/master/documentation/deriverables/R1/BugTracking.md
• References:
  • #31
  • https://www.se.rit.edu/~swen-344/projects/projectdescription.html#R1

Do this on the frontend.

https://www.se.rit.edu/~swen-344/projects/projectdescription.html#r2

• Current Weather
  • The user should be able to customize their location for the weather: They should be able to enter their zip code for the user to enter in their location. The system should save the user's zip code preference (which they can change at any time.) When the user logs out and logs back in then this information should persist.

• Two main additions for functionality include:

  • Stock ticker (Storing information)
  • Calendar (Storing information)
  • Other items as will be defined by customer,

• Testing

  • UI Tester
  • Updated Bug Tracker

• Documentation.

  • Small .pdf document containing:
    • Your version control system link & any appropriate logins
    • Analytics feature for customer. You will need to elicit the precise details with the customer. Something like Google Analytics here is fine.

• A fully implemented system with good usability.
• Your staging & production environments should be mirrors of each other. (We don't have a staging environment)
• Create a virtual directory for the release titled R2. If you are using a different technology than .Net, then do something analogous (you are encouraged to speak about this with your instructor). This means that the release should be http://vm549-x.se.rit.edu/R2/
• You may leave all of your source code in your Version Control System. There is no need to submit the code.
• All data should be stored in your database. Do not plan on storing anything in local files (IE .csv or .xml files)
• Everything should be as functional as possible. Additionally, the application should be much more aesthetically pleasing.

• Database

  • Schema
  • Propagation mechanism
  • Functionality
  • Security (you can discuss this with customer)
    • Tools ran to assess security risks and their results. Additionally, you should provide a mitigation plan for how you would deal with the risks (it will take some research and planning on your part).
    • At least 5 Abuse and Misuse cases.
    • Main areas of vulnerability for your project.

• Application should work in:
  - [ ] Internet Explorer

  • FireFox
  • Various versions of Chrome

Postgres emits a bunch of errors about the user 'postgres' not existing. This only happened after, nginx was added for TLS.

https://letsencrypt.org/getting-started/

Facebook doesn't work very well.

We need to do a presentation for R1.

https://docs.google.com/presentation/d/12yePg9iktnBbb178LpwFKkQqYZ56qSbd6E4JrbzdwBE/edit#slide=id.g4eec738992_0_73

https://docs.seleniumhq.org/

This isn't selenium https://webdriver.io/docs/frameworks.html, but it may be useful as an alternative.

Delete the backend and frontend specific files
Move everything else into docker/
Move the build.sh and adjust paths in the dockerfile

Determine which charting library will be used for displaying stock information.

• https://www.chartjs.org/ I have had good experiences with this library before.

This would be better than the current solution of using alert()

When I try to login with the credentials provided, the app doesn't log in. Gives you a could not authenticate alert.

I tried this with and without incognito. Also, I tried Facebook login with and without incognito.

• Weather: The page should show the current weather for RIT (14623)

Proper development & "production" environment setup.

• Virtual machines
• Calendar - (No need to store information that is an R2 requirement)
• Bug Tracking
  • How many bugs did you collect
  • How many open bugs do you have? And why are they open
  • How has the bug collection/mitigation process helped or hurt your project
  • This can all be placed into a small pdf.
• Version control system
  • If you use GitHub, please give me access (dan7800)
• Main page setup
• Facebook/Twitter tie in
• My test account is [email protected] so please add this to your FaceBook/Twitter app/project if necessary.
• You MAY need to add me as a test user.
• You may also create a test Facebook user. If you do, provide the approriate login/password in your documentation.
• You may leave all of your source code in your Version Control System. There is no need to submit.
• Small .pdf document containing: Your version control system link & any appropriate logins

Stock ticker (Retrieve information from existing external API's)

• You should have a stock page for any ticket symbols that the user may "punch in". Displayed data should include:
  • Current price
  • Day's high
  • Day's low
  • Yearly high
  • Yearly low
• An interactive chart of the stock (not just a retrieved image)

Updated documentation (design & requirements).

• This includes updates & necessary additions to all documents.

• Make sure that your website is publicly accessible to the outside world. This is required for the 1st deliverable and I encourage you to test your application early & often.

• "Final" deliverable is on the production website.

Testing

• Basic Set up of UI Tester (Selenium, iMacros etc...) Basically, just show that you are working towards implementing this for R2. A screen shot of this implementation (in a .pdf form) is fine.
• Other items as will be defined by customer.
• You DO NOT need to set up a SQL Database for R1.

A Document with the following:

• Your site URL
• Login information on your site. Please provide me with "dummy" login information needed to access your site (if applicable).
• A brief readme

Not sure if its a repo or env problem.

Why does this keep happening? 😢

Determine which calendar rendering library will be used.

Will stock prices only be recorded when a purchase or sale is made, or will a separate thread scrape some other API to build our own dataset.

What stock trading api do we want to use?
https://iextrading.com/developer/docs/ looks nice.

The post functionality in the app should create a post that persists in facebook.

Logging into the site using FB authentication while already having a Facebook account logged in yields the following error: "App Not Setup: This app is still in development mode, and you don't have access to it. Switch to a registered test user or ask an app admin for permissions." User most go to incognito/private mode to log in.

Do we have a logout button?
I feel like login status/ route redirection contingent on authentication is a problem that needs to be tackled.

- [ ] verify that get_user_id_from_facebook() works

• Consider making events slicing based on local time, not UTC.

• Consider moving the /users route to / from /auth

• Make an actual return type for the (UserStockResponse, f64) response.

• Use !(Never) type in get_num_servers_up() when the never type becomes standard. (unlikely)

• Point the assets directory at the frontend's build directory.

• We don't use twitter as oauth.
• We need a different api dependency for the fb feed.
• Nginx sits between server_bin and frontend.
• More specific frontend testing.

There should be some validation step to prevent the post feature from posting to facebook if there is no content.

What weather API should we use?

• https://darksky.net/dev Is a good source, but it does require an account. If anyone can find anything else that doesn't need an account, please suggest.

• store calendar events in backend.
• get events from the backend.
• write events-today component for main page.

• add buy/sell options.
• integrate buy/sell operations w/ backend.
• get buy/sell history from backend, display total profit/loss.

Jenkins or TravisCi, whatever prof. wants.

I think we came to consensus on this one, but I forgot.

• Facebook
• Twitter

Implementation requirements

• Get OAuth token from provider
• Get feed for provider.
• Login process should get unique client_id from provider (Backend)

https://github.com/hgzimmerman/SWEN344-web-project/blob/master/documentation/Requirements.md

User stories are required.

• When receiving a stock's information there should be a chart under the table.
• It should be an interactive chart of the stock (not just a retrieved image)
• https://www.tradingview.com/HTML5-stock-forex-bitcoin-charting-library/
• https://canvasjs.com/

Creating a Post on FB should also trigger the app to re-fetch recent posts.

I think we want one of the RIT Ubuntu VMs.
Setting up the backend environment there should be easy - just install nix and rustup.

The custom_error function used with warp to write nice messages for errors only takes into account 404 errors.

There is another internal warp error enum that needs to be matched as well that contains errors for things like calling an endpoint with the wrong method.

Size of input textbox should be constrained, and surrounding layout should dynamically respond to variable sized elements.

• specify zip code.
• save zip code via apis (https://github.com/hgzimmerman/SWEN344-web-project/blob/master/documentation/API.md)

business crate will handle business logic and type conversions and reexport functions from db.
server will only handle routing glue.
db will require a refactor to decouple static methods from schema-bound types so individual functions can be reexported.