make a half-baked tarball (#221)

* make a half-baked tarball

Closes #217

Signed-off-by: Xe Iaso <me@xeiaso.net>

* make two tarballs: one with just the vendor, and one with vendor and npm

Signed-off-by: Xe Iaso <me@xeiaso.net>

---------

Signed-off-by: Xe Iaso <me@xeiaso.net>

docs/docs/developer/building-anubis.md

@@ -8,7 +8,11 @@ These instructions may work, but for right now they are informative for downstre
 
 :::
 
-## Tools needed
+## Entirely from source
+
+If you are doing a build entirely from source, here's what you need to do:
+
+### Tools needed
 
 In order to build a production-ready binary of Anubis, you need the following packages in your environment:
 
@@ -50,6 +54,23 @@ make build
 
 From this point it is up to you to make sure that `./var/anubis` ends up in the right place. You may want to consult the `./run` folder for useful files such as a systemd unit and `anubis.env.default` file.
 
+## "Pre-baked" tarball
+
+The `anubis-src-with-vendor` tarball has many pre-build steps already done, including:
+
+- Go module dependencies are present in `./vendor`
+- Static assets (JS, CSS, etc.) are already built in CI
+
+This means you do not have to manage Go, NPM, or other ecosystem dependencies.
+
+When using this tarball, all you need to do is build `./cmd/anubis`:
+
+```text
+make prebaked-build
+```
+
+Anubis will be built to `./var/anubis`.
+
 ## Development dependencies
 
 Optionally, you can install the following dependencies for development:

docs/docs/developer/local-dev.md

@@ -69,7 +69,7 @@ Install `yeet`:
 :::
 
 ```text
-go install within.website/x/cmd/yeet@v1.13.3
+go install within.website/x/cmd/yeet@v1.13.4
 ```
 
 Install the dependencies for Anubis: