25 Commits

Author SHA1 Message Date
Logan Cusano
f5d58d45da Semi functional client webUI
- can update client info for sure
- Working on notifications now
2023-07-22 03:27:39 -04:00
Logan Cusano
62c0504028 Check if the presets exist when going to get them
- Return empty object if no preset file is found
2023-07-22 01:47:09 -04:00
Logan Cusano
5dd27f0bed Ignore local radio presets 2023-07-22 01:46:19 -04:00
Logan Cusano
e0bae665ed Fixed bug when editing node systems
- Name defaulted to new system name
2023-07-22 01:45:32 -04:00
Logan Cusano
598c802b28 Remove specific presets and left an example file if needed for clients 2023-07-22 01:29:47 -04:00
Logan Cusano
ace762fc76 Finalizing Server webUI
Still needed:
- Way to update clients' versions
- Way to delete nodes
- working dashboard
- working search function
2023-07-22 01:19:54 -04:00
Logan Cusano
75156d059e Add new node if node tries to check in with an ID not in the DB 2023-07-21 18:51:55 -04:00
Logan Cusano
abb833840a Update request node checkin in update node 2023-07-21 18:36:21 -04:00
Logan Cusano
11c8a149bb Remove unnecessary online param from webUI update node 2023-07-21 18:31:41 -04:00
Logan Cusano
9c111eda1a Update design on navbar and sidebar 2023-07-21 18:15:51 -04:00
Logan Cusano
31de3a040d Implemented functional method to add a new system to a new through web app 2023-07-16 23:21:05 -04:00
Logan Cusano
318ee7bf91 Implement functioning method to update systems on web app 2023-07-16 22:30:18 -04:00
Logan Cusano
5428ac6144 Update API and add webapp saving 2023-07-16 18:56:47 -04:00
Logan Cusano
e27dd9d9cb Updated NodeCard Design 2023-07-16 16:47:42 -04:00
Logan Cusano
c0927601b9 Update toast creator to display proper date string 2023-07-16 01:54:13 -04:00
Logan Cusano
ef45cf6539 Only show heartbeat toast once HTTP request is complete 2023-07-16 01:51:25 -04:00
Logan Cusano
23bea5f74e Update heartbeat function location and name 2023-07-16 01:50:01 -04:00
Logan Cusano
fc743cbb46 #37 Working Joining and Leaving 2023-07-16 01:43:13 -04:00
Logan Cusano
e522326576 Additional changes for #37
- Updating side bar
- Updating nav bar
- Adding node details page
- Adding controller page
- Updating routes
2023-07-15 23:30:41 -04:00
Logan Cusano
2e22fa66a6 Initial bones for #37 2023-07-15 18:16:42 -04:00
Logan Cusano
6b37a48061 Update jsDoc in utils 2023-07-15 18:15:17 -04:00
Logan Cusano
5d6d86fa47 Update jsDoc in nodeController 2023-07-15 18:14:53 -04:00
Logan Cusano
c35d3f3fa7 Update adminController to use join/leave command wrappers 2023-07-15 18:14:40 -04:00
Logan Cusano
c38bca4144 Add jsDoc to leaveServerWrapper 2023-07-15 17:58:35 -04:00
Logan Cusano
e6332dffc9 Update join command to accept a specific node ID 2023-07-15 17:58:12 -04:00
3 changed files with 29 additions and 28 deletions

View File

@@ -2,13 +2,13 @@
---
The client application communicates with the server through the provided API. Each client instance waits for join requests sent by users through Discord. Once a join request is received, the client uses the SDR application to tune into the specified radio preset. It then establishes a connection to Discord, allowing users to listen to the selected radio preset in real-time.
In addition to its interaction with the server, the client also has its own API and web application. This enables users to directly interface with the client, perform actions specific to the client application, and access relevant information about the connected SDR and radio presets.
Explanation here
## Requirements
---
Requirements here (not modules, that will be installed with npm)
### Hardware
- SBC

View File

@@ -2,11 +2,7 @@
---
The server application acts as the central hub within Discord, providing various functionalities and serving as the main point of communication for the clients. Some of the key features and responsibilities of the server include:
- **RSS Feed Updates**: The server periodically updates text channels with RSS feed updates, keeping users informed about the latest news or information.
- **Server Management Functions / User Requests**: The server includes management functions that allow administrators to control and configure various aspects of the server environment. Users can interact with the server through Discord commands, which range from requesting specific radio presets to updating RSS feeds.
- **API and Web Front End**: The server exposes an API and web front end, providing an interface to view and control all the online clients. This allows users to monitor and manage the available radio presets, as well as perform various administrative tasks.
Overview here
## Requirements

View File

@@ -1,27 +1,32 @@
# Project Overview
This project is a multi-layered application consisting of client and server applications. Its main purpose is to enable the use of Software-Defined Radios (SDRs) and Raspberry Pi (or similar Single Board Computers) to listen to radio frequencies in Discord voice channels. The project is designed to provide a seamless integration between the SDR hardware and the server with Discord commands.
## Server Application
The server application acts as the central hub within Discord, providing various functionalities and serving as the main point of communication for the clients. Some of the key features and responsibilities of the server include:
- **RSS Feed Updates**: The server periodically updates text channels with RSS feed updates, keeping users informed about the latest news or information.
- **Server Management Functions / User Requests**: The server includes management functions that allow administrators to control and configure various aspects of the server environment. Users can interact with the server through Discord commands, which range from requesting specific radio presets to updating RSS feeds.
- **API and Web Front End**: The server exposes an API and web front end, providing an interface to view and control all the online clients. This allows users to monitor and manage the available radio presets, as well as perform various administrative tasks.
#### [Read more about the Server](https://git.vpn.cusano.net/logan/DRB-CnC/src/branch/master/Server)
# Discord Radio Bot: Command & Control
---
## Client Application
The client application communicates with the server through the provided API. Each client instance waits for join requests sent by users through Discord. Once a join request is received, the client uses the SDR application to tune into the specified radio preset. It then establishes a connection to Discord, allowing users to listen to the selected radio preset in real-time.
Project overview here
In addition to its interaction with the server, the client also has its own API and web application. This enables users to directly interface with the client, perform actions specific to the client application, and access relevant information about the connected SDR and radio presets.
## Requirements Overview
#### [Read more about the Client](https://git.vpn.cusano.net/logan/DRB-CnC/src/branch/master/Client)
---
---
### Server Requirements
#### Server: Discord Bot Requirements
### Client Requirements
#### Client: Discord Bot Requirements
## Troubleshooting
Check the [wiki](https://git.vpn.cusano.net/logan/DRB-CnC/wiki)
## Server
---
Explanation and overview here
## Client
---
Explanation and overview here
## Discord Bot
---
Explanation and overview here