Fela Maslen
e62f0c4488
fix: separate services instead of nginx ingress
|
il y a 5 ans | |
|---|---|---|
| .. | ||
| public | il y a 5 ans | |
| src | il y a 5 ans | |
| .dockerignore | il y a 5 ans | |
| .env.example | il y a 5 ans | |
| .env.test | il y a 5 ans | |
| .eslintrc.js | il y a 5 ans | |
| .gitignore | il y a 5 ans | |
| .prettierrc.js | il y a 5 ans | |
| Dockerfile | il y a 5 ans | |
| Makefile | il y a 5 ans | |
| README.md | il y a 5 ans | |
| builder.Dockerfile | il y a 5 ans | |
| nginx.conf | il y a 5 ans | |
| package.json | il y a 5 ans | |
| tsconfig.json | il y a 5 ans | |
| yarn.lock | il y a 5 ans | |
README.md
gmus-web
This is a frontend web app for use with the gmus backend.
Scripts
yarn start
Runs the app in the development mode.
yarn test
Runs tests
yarn build
Builds app
Architecture
Global app
This is the main part of the app. It is responsible for handling:
- Global state such as which song is playing, and the current time
- Connections to the API, through a websocket
- Sharing state with other clients, and responding to updates from the API
- Playing music, through an HTML element
- User input, to decide which actions to take
- Display, to let the user know the state of things
UI
This is the part of the app which implements user interaction. It is responsible for handling:
UIs follow a common model and are built into separate bundles, then lazily loaded.
The following UIs are implemented:
cmus
This is based heavily on the cmus ncurses-based music player, and is essentially a web-based client with vim-like bindings for navigation.