Update server/README.md
This commit is contained in:
parent
c3bfc8c354
commit
ebc9831c93
|
@ -43,6 +43,11 @@ HamClock's built-in port 8080 service, or it can use X11. The X11 method is
|
||||||
highly recommended when it can be used, because it does not occasionally
|
highly recommended when it can be used, because it does not occasionally
|
||||||
freeze when HamClock is on certain screens like the port 8080 backend does.
|
freeze when HamClock is on certain screens like the port 8080 backend does.
|
||||||
|
|
||||||
|
A variant on the X11 backend, called the SaaS backend, is also available. It
|
||||||
|
works the same way, except it starts HamClock on its own and stops it when
|
||||||
|
the user disconnects. This is intended for cloud/SaaS environments that may
|
||||||
|
run multiple HamClocks for different users.
|
||||||
|
|
||||||
### Port 8080
|
### Port 8080
|
||||||
|
|
||||||
The Port 8080 backend just requires a running instance of 800x480 HamClock.
|
The Port 8080 backend just requires a running instance of 800x480 HamClock.
|
||||||
|
@ -59,6 +64,10 @@ For example:
|
||||||
|
|
||||||
Replace :1 with the desired display number.
|
Replace :1 with the desired display number.
|
||||||
|
|
||||||
|
### SaaS
|
||||||
|
|
||||||
|
The SaaS backend
|
||||||
|
|
||||||
### Custom
|
### Custom
|
||||||
|
|
||||||
If you write your own backend, just put it in the `backends` folder and
|
If you write your own backend, just put it in the `backends` folder and
|
||||||
|
|
Loading…
Reference in New Issue
Block a user