Closed paul-tqh-nguyen closed 5 years ago
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/d30ed5ce5d61659ebdbf6f09823d9f1941dee74b
This is a commit containing some useless templated React skeleton code that hasn't at all in any way been fitted towards our needs yet.
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/cd9f9f8646510f29fb0d61ede68fe55ef1e38239
This patch adds a manifest.json.
It's still all boiler plate stuff.
To be fixed later.
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/fdae3d0e2c0b1fe27777f0384aa8761f1c68db6c
This patch makes it so that the following now install the necessary libraries to get our front end started and starts our front end server:
./arxiv_as_a_newspaper.py -start-front-end-server
It also has some nice pretty printing.
It also gracefully handles keyboard interrupts, which is (as the printing shows when we invoke our front end as described above), the preferred way of exiting the front end.
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/dad9a9496563a560ac13dfa0ff01d0ed93fa5f0a
This patch makes the following top-level CLI command work:
./arxiv_as_a_newspaper.py -end-to-end
This will not work completely, it's just that our ETL and front end are now sufficiently unstubbed to make this hook work.
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/c51ff0d26c8a9887a475d7d818a14213d5e7618b
This patch fixes a bug introduced by ancillary refactoring in previous patches.
We were attempting to start our server prior to installing the necessary libraries.
That made it impossible to start the front end server on a fresh check out.
Progress Patch: https://github.com/paul-tqh-nguyen/arxiv_as_a_newspaper/commit/4d484ab1ba3f5c34a92f1ae3e395b14360856683
The commit in c51ff0d used a stale file, which caused incorrect syntax, which caused immense problems in terms of functionality.
This patch fixes those issues.
Manual testing has shown the top level CLI does start a working server if we use a fresh checkout. That suffices to close this issue.
This task is to get some basic "Hello World" type of front end working.
There doesn't have to be content.
It does have to be hooked up to our top-level CLI that initializes it.