zarkana / im-telling-the-story Goto Github PK

This issue seeks to determine what the home page looks like. Without writing any code, draw some boxes and get a rough outline, for our first draft of the home page.

This could literally be sketches on the back of a napkin. Don't do any code yet. We will create a coding based issue in the next task.

In /backend/ , create an extremely simple service, in which you can send a GET and receive a 200 response with any message you like. Memes are preferred here.

Append to the /backend/README.md instructions on how to run this service. Are there any system requirements?

We will be deploying to Linux, so include specific instructions in the context of Linux. Any packages required, etc etc

This can be however you want and can collide.

Since maxlength is the same for every user per a round it makes more sense to move maxlength to the round rather than in the submission

Changes should be reflected in SQL scripts as well as on the SqlDBM page

https://app.sqldbm.com/MySQL/Share/Fa6jlrZ4JJOjJh0bCzjcdkGFrngIE8md_DYjF4jNYw0

We now have a backend service that serves HTTP requests! When we call vagrant up, we should now have a front end web service running on one port, and a back end service running on another port. Completion of this ticket means that vagrant up will also bring up the backend service running on whatever port number you like.

fyi. Port numbers below 1024 are for root/priveleged users. So just to be safe, use a number greater than 1024

Ability for users to create account with a minimum of google credentials and associate the credential with access to write and read from the DB.

Waiting on this prior to implementing API integration.

The front end will soon be making API calls to our backend! In our vagrant environment, these calls will be made to localhost. In a production environment, these calls will probably point to an IP address that is NOT localhost.

A possible solution for this, is to tell Joseph to always make HTTP calls to api.imtellingthestory.com. That way, Joseph can write code that all points to the same host. Joseph shouldn't have to worry about IP addresses at all; it's not the responsibility of the front end to do this.

This means that we need our vagrant machine to always resolve this:
api.imtellingthestory.com -> 127.0.0.1

Update our vagrant file to make only api.imtellingthestory.com always resolve to 127.0.0.1

The tricky part will be the idempotency. If I run vagrant up, it's easy to just append to /etc/hosts. If I run vagrant up a second time. We don't want to have two identical entries in /etc/hosts!

Hint, maybe use grep to detect if the line already exists in /etc/hosts before doing an append.

Pick a good one I guess. Or pick the worst one humanly possible to be funny lmao

set up this bad boy: https://github.com/facebook/create-react-app
also, you need to install the latest nodejs if u haven't.
make a component too if can idk

can do other react starter kit too if u find one