Updated the readme a little.
This commit is contained in:
22
Readme.md
22
Readme.md
@@ -5,19 +5,31 @@ but with clients and servers exchanging binary messages
|
||||
(which can be compressed automatically) rather than human-typed text.
|
||||
|
||||
Right now, it will use ax25 connected sessions through AGWPE,
|
||||
though I make add an unconnected protocol using UI later on..
|
||||
though I may add an unconnected protocol using UI later on..
|
||||
|
||||
I'm planning several features like:
|
||||
Features completed:
|
||||
|
||||
- Object CRUD operations
|
||||
- Podman containerized job orchestrator
|
||||
- automatic compression for all RF communication
|
||||
- messages for other users
|
||||
- RF beacon
|
||||
- administration over RF
|
||||
|
||||
Features in-progress and working to some extent:
|
||||
|
||||
- Send and searching messages to/from other users
|
||||
- object storage/retrieval
|
||||
- running user-defined scripts or shell commands on the server in containers with podman/docker
|
||||
- Posting, retrieving, and editing public bulletins
|
||||
- Partial Python client wrapper library for the RF 'API'
|
||||
|
||||
I'm considering several other features like:
|
||||
|
||||
- Useful documentation of any variety..
|
||||
- RF beacon
|
||||
- administration over RF
|
||||
- possibly a cron system (again in containers for safety)
|
||||
- maybe an e-mail or an sms gateway (though clever user uploaded scripts could do this instead)
|
||||
- maybe APRS integration through APRS-IS
|
||||
- Kubernetes or possibly simple shell job execution.
|
||||
|
||||
I may also add a TCP/IP interface to this later, since that shouldn't be too difficult. We'll see.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user