💾 Archived View for thebackupbox.net › ~epoch › blog › veilid-8 captured on 2024-12-17 at 10:11:18. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-07-09)

-=-=-=-=-=-=-

misc

previous

next

Since I have veilid-server running constantly now, I figured it'd be fun to log any appmessages sent to my node to an IRC channel. This way they won't get lost as easily in the noise of veilid-cli.

Doing this using:

veilid-watch-appmessages >> /var/log/veilid.log

being ran by daemontools, and I have a bot that will tail anything in /var/log and drop it into an IRC channel.

I posted to the fediverse about this a couple days ago.

link to it

I'll restate it pretty much here so you don't have to load that mess.

If you want to send messages between your veilid node and any other, you can do:

enable app_messages
appmessage <node-ID> "a message"

So, to send to me, you'd do:

appmessage VLD0:L68InvIRxdMSa_FFq_OJGq3g4NJ0dIvI14a12p8PvNo 'Hello, epoch!'

when your message arrives I'll see your node-ID as the sender, so I can reply without you having to tell me your node ID.

let's see... what else have I done with veilid recently...

I finished doing the bootstrap server thing. I switched the domain to veilid.thebackupbox.net.

and I made a cert and key so I could enable the TLS stuff in veilid's config.

I use acme_tiny.py and a Makefile to do my cert stuff.

here's the source for that shit

it appears to all work, but I haven't poked at it a bunch yet.

If you want to enable the ws and wss you'll need to put a url option in.

it seems like the tcp, ws, and wss all listen on the same tcp port. 5150.

here's the relevent bits of my config...

client_api:
  enabled: true
  listen_address: enzo:5959
logging:
  system:
    enabled: true
    level: info
  terminal:
    enabled: false
core:
  network:
    tls:
      certificate_path: /etc/letsencrypt/veilid.crt
      private_key_path: /etc/letsencrypt/keys/veilid.key.pem
      connection_initial_timeout_ms: 2000
    protocol:
      tcp:
        connect: true
        listen: true
        public_address: 'veilid.thebackupbox.net:5150'
      udp:
        connect: true
        listen: true
        public_address: 'veilid.thebackupbox.net:5150'
      ws:
        connect: true
        listen: true
        public_address: 'veilid.thebackupbox.net:5150'
        url: 'ws://veilid.thebackupbox.net:5150/ws'
      wss:
        connect: true
        listen: true
        public_address: 'veilid.thebackupbox.net:5150'
        url: 'wss://veilid.thebackupbox.net:5150/ws'

I have the enzo hostname set in /etc/hosts to include both 127.0.0.1 and my LAN IP, so I can connect to the client API port from other computers on my network.

um...

I think that's it for now.

I've been posting links to these blog posts into the fediverse, so I guess I'll start including links to those posts at the end of blog posts.

fedipost for this blog post