cjbrunner / chrisweb Goto Github PK

0.0 1.0 0.0 203 KB

JavaScript 72.76% CSS 7.57% TypeScript 6.26% Dockerfile 11.92% Shell 1.50%

chrisweb's Introduction

This is a Next.js project bootstrapped with create-next-app. It's mostly just a personal space to for me to practice with Next.js and React, but I also have a little Sonos app that talks to the Sonos Node API I have running on a Raspberry Pi elsewhere in the house. Eventually it's going to also host code to access my old blog locally if I want to look up something there.

Sonos Controller

A front-end React app designed to interface with a Sonos Node API running elsewhere on the network. For situations where the official Sonos control apps are unavailable or is otherwise not wanted.

Getting Started

To run the development server:

npm run dev

Open http://localhost:3000/sonos with your browser to see the Sonos controller app.

Main app root page is src/app/sonos/page.tsx.

Building and deploying

To build a production server

npm run build

To run server after building

npm run start

Docker

This application can also be Dockerized.

Prerequisites

Docker must be installed
User must have permission to access Docker

Updater script

There is a simple script that automatically builds, stops, and starts a new Docker-based server.

Blog viewer

TBD

chrisweb's People

Contributors

Watchers

chrisweb's Issues

Controls don't respect zone

Looks like the controls will only control the "office" zone, not the current zone.

Have app auto-start on server

Currently running manually via the command line:

npm run build
nohup npm run start

Not ideal.

Set up auto-start of app at server boot-up (docker run -d --restart)
Support for updating the app and restarting if necessary (updatedockerImage.sh)
Stop old server

Remove HTML element from useState hook

Use a useRef used for storing that sort of thing, as most built in components support ref and that might simplify things

Add polling to keep song info up-to-date

Currently, the song info displayed will remain the same until the page refreshes, so new song info won't change even if the song playing changes. Looks like some kind of polling is required, since there is no signal sent from the server on song changes.

Implement useReducer to combine state

Use useReducer as soon as there is more than one related bit of state, i.e. isLoading and the sonosInfo. Each set state call triggers its own re-render, so combining them into a reducer call cuts down on those.