Compare commits

...

3 Commits

Author SHA1 Message Date
Brian O'Reilly 49cba9fe7c addenda 2025-11-02 16:01:19 -05:00
Brian O'Reilly 8d0240340a typo 2025-11-02 16:01:19 -05:00
Brian O'Reilly c7852e4230 Deployment, and post deployment notes and problems in TODO.org 2025-11-02 16:01:19 -05:00
1 changed files with 29 additions and 0 deletions

View File

@ -9,6 +9,34 @@
- [X] Set up DNS
- [X] Create user accounts
* Deploy the system
- [X] Install and configure HAproxy
- [X] Create a user to contain asteroid
- [X] Checkout asteroid in ~asteroid on b612
- [X] Build the docker containers
- [X] Build asteroid from the sources
- [X] Configure HAproxy to front http://asteroid.radio/ -> http://localhost:8080/
- [X] Set ASTEROID_STREAM_URL in ~asteroid/.bashrc
- [X] Start the docker containers for liquidsoap, icecast, and postgresql
- [X] Start asteroid, check the stream (Underworld:Juanita/Kiteless)
- [X] Announce that the system is live in #asteroid.radio
** PROBLEMS
1) Liquidsoap is exposing its management console via telnet on the exterior network interface of b612.asteroid.radio
2) icecast is also binding the external interface on b612, which it
should not be. HAproxy is there to mediate this flow.
3) We're still on the built in i-lambdalite database
4) The templates still advertise the default administrator password,
which is no bueno.
5) We need to work out the TLS situation with letsencrypt, and
integrate it into HAproxy.
6) the administrative interface should be beefed up.
5.1) Deactivate users
5.2) Change user access permissions
7) User profile pages should probably be fleshed out.
8) the stream management features aren't there for Admins or DJs.
9) The "Scan Library" feature is not working in the main branch
* Server runtime configuration [0/1]
- [ ] parameterize all configuration for runtime loading [0/2]
- [ ] strip hard coded configurations out of the system
@ -20,6 +48,7 @@
- [ ] Configure radiance for postres.
- [ ] Migrate all schema to new database.
** [X] Page Flow [2/2] ✅ COMPLETE
- [X] When a user logs in, their user profile page should become the
root node of the app in their view.