booger deploy v0.0.3-sigma

No one is using this but upgrade if you are because there were a few important bugs fixed.

breaking changes

We changed the bind config param to hostname to be easier to use with docker.

fixes

• nip11 json property names are now cased properly
• stats and limits plugs had bugs that would reject valid subscriptions

enhancements

• index.html can now be used as a homepage for your booger relay

This is the first release deployed to https://booger.pro

booger art v0.0.2-sigma

This release mostly adds an updated version number to the release. Also polish: more concise logs and some startup ascii art.

booger race v0.0.1-sigma

This fixes a major oversight in booger plug communication. v0.0.0-sigma did not correctly associate messages sent to booger plugs with messages received from booger plugs. I'd been living that sweet single threaded life for too long.

If there's some adventurous soul out there playing with booger, 10/10 recommend upgrading.

initial booger release - achoo

We've done it guys. Grab an orange slice and take a knee.

This is our first ever booger release. I have no idea how well this code will run in prod but it's certainly okay to play around with.

One of booger's goals is to be simple enough that a pleb can run it and pleb dev can modify it. No one enjoys reading other people's code (unless its fantastic) so I'm sorry you might choose to read mine, but I tried to make it short.

This release is currently clocking in at 1753 LOC including db migrations, db migrator (which should probably be spun into an external module), booger plugs, newlines, comments, and the embedded configuration file excluding tests.

• btw I got the LOC number with the following command: wc -l $(find . -name "*.js" -not -path "./test/*")

executables

I've compiled booger for all the targets deno cross compiles to: x86_64-unknown-linux-gnu, x86_64-pc-windows-msvc, x86_64-apple-darwin, aarch64-apple-darwin and provided them as release assets.

There are two executables for each target:

1. normal - runs with the same restrictions that you run most things on your computer with
2. secure - a runtime-restricted executable
   • booger can only communicate on loopback
   • booger can only access relevant environment variables
   • booger can only write to ./booger.jsonc
   • booger can only read from ./booger.jsonc and ./plugs/
   • read more about booger's runtime restrictions on deno.land

naming

Release assets are given names formatted like: booger-VERSION-PERMS-TARGET.zip

If you want a normal linux release, you'd pick booger booger-v0.0.0-normal-x86_64-unknown-linux-gnu.zip
If you want a secure windows release, you'd pick booger booger-v0.0.0-secure-x86_64-pc-windows-msvc.zip