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:
- normal - runs with the same restrictions that you run most things on your computer with
- 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.jsoncand./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