Skip to content
C.W.K.
Lesson 02 of 04 · published

The Repository Has One Listener, and It Is Opt-In

~12 min · gateway, listener, bind

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

The Engine Stays Portless

firebrand gateway is the one listening program in the repository. The engine that authors still opens no port. The gateway binds this host's mesh address or loopback. A bind to every interface, a LAN address, or a public address is refused in structure. There is no flag that widens it. Starting the gateway is an operator choice. Not starting it is the cleanroom default.

Inside, supervision copies the Mac host: a control child for catalog and sessionless reads, one engine child per live session, the same frame cap, the same teardown when the parent dies. A websocket on the outside is translated to the same stdio the Mac already speaks. The loop does not learn that it is remote.

One listener, copied supervision, no second loop. If remote needed a different engine, you would be measuring two products and calling them one.

Start Is a Recorded Act

Gateway start and stop are lines in the gateway log. Session attach, claim, refuse, child spawn and exit are lines. The session notebooks remain the lab notebooks. The gateway log is the door log. Mixing them would make resume feed a model a firewall. The model does not need to know that a phone is watching. It needs the same fold the terminal already uses.

Code

The only listener verb·bash
firebrand gateway
# binds mesh-or-loopback; refuses a public bind
# engine children still speak client/1 over stdio
# not starting this is the product, not a missing feature

External links

Exercise

Write two bind stories: one that should start, one that must refuse. The refusing story should be 'listen on every interface so friends on the cafe wifi can try.' There is no flag for that.
Hint
Mesh or loopback. Everything else is a different product.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign in — Please sign in to comment.

No comments yet — be the first.