feat: add ability to run an exposed container

This commit is contained in:
2025-07-11 21:21:12 +02:00
parent 17fcd053ac
commit 56df0f204b
4 changed files with 52 additions and 6 deletions

12
NETWORKING.md Normal file
View File

@@ -0,0 +1,12 @@
# Networking
We've got multiple hosts potentially in play, and multiple containers that wants
to expose themselves on the primary host, but only 1 process can take a tcp port
on the same host at a time.
1. The primary instance, will bind to common tcp ports as required (80, 443) can
be changed.
1. TODO: TLS termination
1. Will send traffic to peers hosting their versions of a url.
1. On the peers, each container will bind to a port (TBD), maybe we will do some
long running connections instead. SOCK protocol