Server version of this app, for no public ip servers #157

New issue

Open

opened 2026-06-09 02:36:04 +00:00 by gesu · 2 comments

gesu commented

2026-06-09 02:36:04 +00:00

(Migrated from codeberg.org)

Description

A server version of this app.

Use Case

One of many reasons for why use this app: no public ip (ISPs with NAT or CGNAT for 5g/4g users), had own server, but can't point a domain to it because of that, want to use on an own server for this and no a mobile device

Possible Implementation

A server versión, for traditional linux servers or something to run it to point a relay, and use a client app login in this server or the relay server

Additional Context

If you have the need of connect a relay its because, don't have a public ip and also you don't have a VPS to tunnel it.

PD=You blow my mind with this, really great app and the idea, thanks

## Description A server version of this app. ## Use Case One of many reasons for why use this app: no public ip (ISPs with NAT or CGNAT for 5g/4g users), had own server, but can't point a domain to it because of that, want to use on an own server for this and no a mobile device ## Possible Implementation A server versión, for traditional linux servers or something to run it to point a relay, and use a client app login in this server or the relay server ## Additional Context If you have the need of connect a relay its because, don't have a public ip and also you don't have a VPS to tunnel it. PD=You blow my mind with this, really great app and the idea, thanks

tom79 commented

2026-06-09 05:40:42 +00:00

(Migrated from codeberg.org)

A Linux version already exists (AppImage and deb), running the same backend as mobile. Logging a client into the relay is also already what the app does today.
The new part is the rest of what you describe: running it headless on your own server, with the UI separated out. The current Linux app is a desktop app with a window, so it does not fit a headless server. But a separate web UI that connects to the backend running on the machine is possible without changing anything in the model. The backend keeps running with its keys on the machine, and the web UI is just a remote view of its state. Exposing account control over the network means building a whole read and write API, secured with an OAuth connection.
So it is real work, but two separate pieces: a full API in front of the backend, and running the app as a headless service without the UI. I will look into it.

A Linux version already exists (AppImage and deb), running the same backend as mobile. Logging a client into the relay is also already what the app does today. The new part is the rest of what you describe: running it headless on your own server, with the UI separated out. The current Linux app is a desktop app with a window, so it does not fit a headless server. But a separate web UI that connects to the backend running on the machine is possible without changing anything in the model. The backend keeps running with its keys on the machine, and the web UI is just a remote view of its state. Exposing account control over the network means building a whole read and write API, secured with an OAuth connection. So it is real work, but two separate pieces: a full API in front of the backend, and running the app as a headless service without the UI. I will look into it.

gesu commented

2026-06-09 19:59:38 +00:00

(Migrated from codeberg.org)

all right, I'll check out