Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

The Un-bodging: Rework to proper backend/frontend #4

Open
3 tasks
LunNova opened this issue Feb 22, 2016 · 2 comments
Open
3 tasks

The Un-bodging: Rework to proper backend/frontend #4

LunNova opened this issue Feb 22, 2016 · 2 comments

Comments

@LunNova
Copy link
Contributor

LunNova commented Feb 22, 2016

Currently we're manually copying JSON files produced by the backend to be rendered. This is a bit rubbish.

  • Determine whether back-end/front-end should be in separate repos?
    • Split from different branches to different repos
    • Leave as is (separate branches in one repo)
    • Join in to one branch, with better folder structure
  • Pick server-side technology for back-end API
    • Jetty + Jackson (already using Jackson)
    • Jetty + Jersey + Jackson
  • Change front-end to read from proper API endpoints instead of loading from linked.json
@ClarSco
Copy link
Member

ClarSco commented Feb 22, 2016

I think we should either split up the branches into separate repositories as the current situation is unsatisfactory and I think that having both parts on the one branch will be far too cluttered.

@ClarSco
Copy link
Member

ClarSco commented Feb 22, 2016

+1 for using proper API endpoints

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants