Our great sponsors
-
Paperless-ng
Discontinued A supercharged version of paperless: scan, index and archive all your physical documents
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.
On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.
On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.
On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.
On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.